Triple
T28549445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Todd Eldredge |
E722839
|
entity |
| Predicate | turnedSeniorInternational |
P31749
|
FINISHED |
| Object | late 1980s |
—
|
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: late 1980s | Statement: [Todd Eldredge, turnedSeniorInternational, late 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnedSeniorInternational Context triple: [Todd Eldredge, turnedSeniorInternational, late 1980s]
-
A.
turnedSenior
chosen
Indicates that an entity has transitioned into senior status or a senior role relative to a previous state or position.
-
B.
isSeniorTo
Indicates that one entity holds a higher rank, status, or level of authority than another.
-
C.
seniorMember
Indicates that one entity holds a higher-ranking or more experienced membership status within a group, organization, or context relative to others.
-
D.
transitionAge
Indicates a change in state or status of an entity from one defined phase, condition, or category to another at a particular point or period in time.
-
E.
retiredTo
Indicates that an entity has permanently left active service or work and taken up residence or status in a particular place or role as their retirement destination.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6500f8ae48190b4f5bd98b505c037 |
completed | May 2, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:41 a.m.