Triple
T1420102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberdeen F.C. |
E30204
|
entity |
| Predicate | managerTenureEnd |
P4346
|
FINISHED |
| Object | 1986 (Sir Alex Ferguson) |
—
|
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: 1986 (Sir Alex Ferguson) | Statement: [Aberdeen F.C., managerTenureEnd, 1986 (Sir Alex Ferguson)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managerTenureEnd Context triple: [Aberdeen F.C., managerTenureEnd, 1986 (Sir Alex Ferguson)]
-
A.
teamTenure
Indicates the duration or length of time an entity has been part of a particular team.
-
B.
officeholderEndTime
chosen
Indicates the time or date at which a person’s term in a particular office or position comes to an end.
-
C.
activeYearsEndTime
Indicates the point in time when an entity’s period of activity or operation comes to an end.
-
D.
retirementDate
Indicates the date on which an entity stops its active role or service, typically marking the end of its professional or operational period.
-
E.
lifeTenure
Indicates that an individual holds a position or office for the duration of their lifetime, without a fixed term limit or routine reappointment.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c40764ec8190b85de6befcb20dda |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.