Triple
T31655549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Future Ted Mosby |
E807848
|
entity |
| Predicate | ageRelativeToTedMosby |
P125146
|
FINISHED |
| Object | older |
—
|
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: older | Statement: [Future Ted Mosby, ageRelativeToTedMosby, older]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRelativeToTedMosby Context triple: [Future Ted Mosby, ageRelativeToTedMosby, older]
-
A.
ageRelativeToVincentChase
Indicates how an entity’s age compares to the age of Vincent Chase (e.g., younger, older, or the same age).
-
B.
relativeAgeInference
Indicates an inferred ordering of ages between entities, specifying which one is relatively older or younger based on available information.
-
C.
relativeAgeStatus
chosen
Indicates a comparative relationship specifying how the age of one entity relates to the age of another (e.g., older, younger, or same age).
-
D.
riftAge
Indicates the age or time since formation of a geological rift or rift-related feature.
-
E.
hasRelativeAge
Indicates that one entity has an age that is defined or compared in relation to the age 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a95e38ac819096c03f2b9872260f |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:55 p.m.