Triple

T29188199
Position Surface form Disambiguated ID Type / Status
Subject Legacy era E739926 entity
Predicate setApproximately P9773 FINISHED
Object over 100 years after the Battle of Yavin 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: over 100 years after the Battle of Yavin | Statement: [Legacy era, setApproximately, over 100 years after the Battle of Yavin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: setApproximately
Context triple: [Legacy era, setApproximately, over 100 years after the Battle of Yavin]
  • A. representsApproximately
    Indicates that one entity serves as an inexact or close-but-not-exact representation or value of another entity.
  • B. containsApproximately
    Indicates that one entity holds or includes another entity in a quantity or proportion that is close to, but not exactly, a specified amount.
  • C. hasApproximateValue chosen
    Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
  • D. holdsApproximatelyFor
    Indicates that a condition, relation, or value is valid only to an approximate degree or within a tolerance, rather than holding exactly.
  • E. hasApproximateUse
    Indicates that one entity is used for a purpose that is similar to, but not exactly the same as, the use or function of another entity.
  • 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_69f07cb8033c8190b8807e219a14333d completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f66388afe48190a68caf56c9745007 completed May 2, 2026, 8:50 p.m.
PD Predicate disambiguation batch_69f65c24f8b48190af81b575f3c15be5 completed May 2, 2026, 8:18 p.m.
Created at: April 28, 2026, 12:01 p.m.