Triple
T24318690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1902 Ibrox disaster |
E612894
|
entity |
| Predicate | replayResult |
P155540
|
FINISHED |
| Object | Scotland 2–2 England |
—
|
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: Scotland 2–2 England | Statement: [1902 Ibrox disaster, replayResult, Scotland 2–2 England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replayResult Context triple: [1902 Ibrox disaster, replayResult, Scotland 2–2 England]
-
A.
replayedOn
Indicates that an event, performance, or recording was played again on a particular medium, platform, or channel.
-
B.
hasReplay
Indicates that an event, action, or interaction is available to be viewed or experienced again in a recorded or reconstructed form.
-
C.
playResult
Indicates the outcome or consequence produced by a particular play or action within a sequence of events.
-
D.
replayFrequency
Indicates how often an event, action, or sequence is repeated or played back over a given period.
-
E.
finalReplayRequired
Indicates that a concluding or definitive replay of an event or process is required to be performed.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292a916c8819096d018e7ffaf483b |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:47 a.m.