Triple
T3469421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Cup final 1975 |
E73216
|
entity |
| Predicate | Leeds UnitedCompetition |
P49148
|
FINISHED |
| Object | English club |
—
|
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: English club | Statement: [European Cup final 1975, Leeds UnitedCompetition, English club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Leeds UnitedCompetition Context triple: [European Cup final 1975, Leeds UnitedCompetition, English club]
-
A.
leagueTitleWonWithLeedsUnited
Indicates that the subject won a league title while playing for or managing Leeds United.
-
B.
leagueOrCup
Indicates that one entity is a league or cup competition in which the other entity participates or is associated.
-
C.
league2
Indicates that an entity participates in, is a member of, or is otherwise affiliated with a specific sports league or competitive organization.
-
D.
leagueCup
Indicates that an entity is a cup-style competition organized within or by a specific league.
-
E.
leagueUsedFor
Indicates that a particular league is utilized as the context, setting, or organizing framework for some activity, event, or 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb376d288190abac85f2ffa853dc |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:17 p.m.