Triple
T25348455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1951 FA Cup Final |
E635616
|
entity |
| Predicate | editionNumberOfFA CupFinal |
P159109
|
FINISHED |
| Object | 70 |
—
|
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: 70 | Statement: [1951 FA Cup Final, editionNumberOfFA CupFinal, 70]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editionNumberOfFA CupFinal Context triple: [1951 FA Cup Final, editionNumberOfFA CupFinal, 70]
-
A.
FA CupFinalScore
Indicates the final match score in an FA Cup competition, specifying how many goals each team scored in the deciding game.
-
B.
editionNumberAsChampionsLeagueFinal
Indicates that an entity is associated with a specific numbered edition of the Champions League final.
-
C.
editionNumberAsEuropeanCupFinal
Indicates that the subject is identified by its specific sequential edition number as a European Cup final.
-
D.
FA CupWinnerWith
Indicates a relationship where a team is identified as having won the FA Cup together with (i.e., in association with) a particular season, year, or related contextual attribute.
-
E.
FA CupFinalVenue
Indicates the venue where a specific FA Cup final match is held.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498bd7e648190855fcf9e2ee4c762 |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 1:34 p.m.