Triple

T10724346
Position Surface form Disambiguated ID Type / Status
Subject Mishma E252899 entity
Predicate traditionallyLocatedWithin P51070 FINISHED
Object genealogies of Ishmael LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: genealogies of Ishmael | Statement: [Mishma, traditionallyLocatedWithin, genealogies of Ishmael]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionallyLocatedWithin
Context triple: [Mishma, traditionallyLocatedWithin, genealogies of Ishmael]
  • A. locatedInTraditionalRegion
    Indicates that an entity is situated within a specific traditional or historically recognized region.
  • B. hasLocationTraditionallyIdentifiedAs chosen
    Indicates that something is situated in, or associated with, a place that is customarily or historically recognized as its location, even if this identification is not formally verified.
  • C. locatedIn
    Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
  • D. traditionallyFoundIn
    Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
  • E. oftenLocatedAt
    Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
  • F. None of above.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69d6aa5d8be481909a43218b2bfdbe95 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d70d46234081908e147638d0cb7e22 completed April 9, 2026, 2:21 a.m.
PD Predicate disambiguation batch_69d6f30455888190b77f476b8418eaee completed April 9, 2026, 12:29 a.m.
Created at: April 8, 2026, 9:14 p.m.