Triple

T34944410
Position Surface form Disambiguated ID Type / Status
Subject Magnetes E1007814 entity
Predicate ancestralPeopleFor P35417 FINISHED
Object colonists of Magnesia on the Maeander 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: colonists of Magnesia on the Maeander | Statement: [Magnetes, ancestralPeopleFor, colonists of Magnesia on the Maeander]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ancestralPeopleFor
Context triple: [Magnetes, ancestralPeopleFor, colonists of Magnesia on the Maeander]
  • A. ancestralLinks
    Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, another entity.
  • B. ancestralGroup chosen
    Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
  • C. foundingAncestor
    Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
  • D. ancestralStatus
    Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
  • E. hasTribalAncestor
    Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
  • 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_69f76dc5d4308190b77553ee07b1ede6 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f782c98fa08190870b68de2c1ff26a completed May 3, 2026, 5:15 p.m.
PD Predicate disambiguation batch_69f781020cc4819088c40cb8589504e4 completed May 3, 2026, 5:08 p.m.
Created at: May 3, 2026, 4 p.m.