Triple
T35517882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2002–03 Arsenal season |
E1026466
|
entity |
| Predicate | finishedBehind |
P78201
|
FINISHED |
| Object | Manchester United F.C. |
—
|
NE NERFINISHED |
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: Manchester United F.C. | Statement: [2002–03 Arsenal season, finishedBehind, Manchester United F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishedBehind Context triple: [2002–03 Arsenal season, finishedBehind, Manchester United F.C.]
-
A.
finishedAheadOf
Indicates that one entity completed an event, task, or process before another entity, ranking or finishing in a superior or earlier position.
-
B.
finished
Indicates that an entity has completed an action, process, or state, reaching its end point.
-
C.
finishedBehindTeam
chosen
Indicates that one team completed a competition, race, or ranking-based event in a lower (worse) position than another specified team.
-
D.
completedAfter
Indicates that one event or task was finished at a later time than another specified event or task.
-
E.
finish
Indicates that an entity brings an action, process, or state to an end or completion.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.