Triple
T24433814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1971 Ibrox disaster |
E616070
|
entity |
| Predicate | hasMatchResult |
P34554
|
FINISHED |
| Object | Rangers 1–1 Celtic |
—
|
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: Rangers 1–1 Celtic | Statement: [1971 Ibrox disaster, hasMatchResult, Rangers 1–1 Celtic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatchResult Context triple: [1971 Ibrox disaster, hasMatchResult, Rangers 1–1 Celtic]
-
A.
hasMatch
Indicates that one entity corresponds to, aligns with, or is considered an equivalent or suitable counterpart to another entity.
-
B.
matchResult
chosen
Indicates the outcome or final status produced by a particular match or game between participants.
-
C.
hasFinalMatch
Indicates that an entity is associated with a concluding or decisive match in a series, tournament, or competition.
-
D.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
E.
finalFirstMatchResult
Indicates that the referenced result is the first outcome in a sequence that is considered final or decisive for a given matching process.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2978469a081909f17b6955809bbef |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.