Triple
T29376995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyra Nichols |
E745026
|
entity |
| Predicate | retirementFromPerformance |
P2644
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Kyra Nichols, retirementFromPerformance, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retirementFromPerformance Context triple: [Kyra Nichols, retirementFromPerformance, early 2000s]
-
A.
retiredFrom
chosen
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
B.
retiredBy
Indicates that one entity has formally ended the active status, use, or service of another entity.
-
C.
forcedToRetire
Indicates that an entity was compelled, rather than choosing voluntarily, to end their professional role or career.
-
D.
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.
-
E.
retiredAtEvent
Indicates that an entity ceased its professional or active role specifically at the time or in the context of a particular event.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669aeb2208190b5b578c5d94edb63 |
completed | May 2, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:32 p.m.