Triple
T22917361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teila Tuli |
E568768
|
entity |
| Predicate | sumoRetirement |
P2089
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Teila Tuli, sumoRetirement, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sumoRetirement Context triple: [Teila Tuli, sumoRetirement, 1989]
-
A.
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.
-
B.
returnedFromRetirement
Indicates that an entity has resumed an activity, role, or position after having previously retired from it.
-
C.
retiredWithProgram
Indicates that an entity retired from its role, position, or activity specifically through or in association with a particular program.
-
D.
retired
chosen
Indicates that an entity has permanently stopped working in their former occupation or role, typically after reaching a certain age or service duration.
-
E.
retirementTeam
Indicates that an entity is part of, or associated with, a team responsible for handling retirement-related matters for 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807a14648190b5d5f7d926f19320 |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.