Triple
T13838369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roy Keane |
E332587
|
entity |
| Predicate | captaincyPeriodAtManchesterUnited |
P111703
|
FINISHED |
| Object | late 1990s to mid-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: late 1990s to mid-2000s | Statement: [Roy Keane, captaincyPeriodAtManchesterUnited, late 1990s to mid-2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captaincyPeriodAtManchesterUnited Context triple: [Roy Keane, captaincyPeriodAtManchesterUnited, late 1990s to mid-2000s]
-
A.
joinedManchesterUnited
Indicates that an entity became a member of, or signed to play for, Manchester United.
-
B.
yearsAsCaptainEnd
Indicates the point in time or year when an entity’s tenure or period of serving as captain ends.
-
C.
presidencyPeriodAtFCBarcelona
Indicates the time span during which an individual served as president of FC Barcelona.
-
D.
leagueDebutForManchesterUnited
Indicates that an entity made their first league appearance while playing for Manchester United.
-
E.
captainedPremiershipYear
Indicates the year in which an entity served as captain of a team in a premiership (championship) competition.
- F. None of above. chosen
Provenance (4 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02ac6b7c81908d44632d6d628339 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:13 p.m.