Triple
T19363885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tangerines |
E484349
|
entity |
| Predicate | notableManagerTenureEnd |
P41368
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [The Tangerines, notableManagerTenureEnd, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableManagerTenureEnd Context triple: [The Tangerines, notableManagerTenureEnd, 1993]
-
A.
notableHostTenure
Indicates that an entity is recognized for having a significant or distinguished period of serving as a host of something (e.g., a show, event, or program).
-
B.
endOfTenure
chosen
Indicates the point or event at which an entity’s period of holding a role, position, or office concludes.
-
C.
officeholderEndTime
Indicates the time or date at which a person’s term in a particular office or position comes to an end.
-
D.
notableDriverTenure
Indicates that an individual had a significant or distinguished period serving as a driver for a particular entity or organization.
-
E.
notableOfficePeriod
Indicates that an entity held a particular office or position during a specified time period.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619a9ac68819082cf9deadf526156 |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:34 p.m.