Triple
T27797543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Italian Cup |
E702154
|
entity |
| Predicate | notableEnglishWinner |
P2766
|
FINISHED |
| Object | Newcastle 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: Newcastle United F.C. | Statement: [Anglo-Italian Cup, notableEnglishWinner, Newcastle United F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEnglishWinner Context triple: [Anglo-Italian Cup, notableEnglishWinner, Newcastle United F.C.]
-
A.
notableWinner
chosen
Indicates that the subject is a particularly distinguished or prominent winner of the referenced competition, award, or contest.
-
B.
notableAwardWon
Indicates that an entity has received a specific notable award as a winner.
-
C.
notableAwardedFor
Indicates that an award is notable specifically for being given in recognition of a particular work, achievement, or contribution.
-
D.
notableWinnerFeature
Indicates that a winner is distinguished by a particular notable characteristic or attribute.
-
E.
notableFirstWinner
Indicates that the subject is the first and notably recognized winner of the object (such as an award, competition, or title).
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a0039c2d5d48190b8ef2c7ef17d8dc5 |
completed | May 10, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_6a0038e525448190a4c815f51595e78d |
completed | May 10, 2026, 7:51 a.m. |
Created at: April 27, 2026, 5:32 p.m.