Triple
T11402136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allison |
E270137
|
entity |
| Predicate | replacedNameStatus |
P19196
|
FINISHED |
| Object | retired |
—
|
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: retired | Statement: [Allison, replacedNameStatus, retired]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedNameStatus Context triple: [Allison, replacedNameStatus, retired]
-
A.
replacementName
Indicates that one entity serves as a substitute or successor name for another entity, effectively replacing the original designation.
-
B.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
-
C.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
D.
legalStatusAfterRenaming
Indicates the legal status or classification that applies to an entity after it has undergone a renaming.
-
E.
nameStatus
chosen
Indicates the status or condition associated with an entity’s name, such as whether it is current, preferred, alternate, or deprecated.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.