Triple
T24318695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1902 Ibrox disaster |
E612894
|
entity |
| Predicate | ledToInquiry |
P155541
|
FINISHED |
| Object | official inquiry into stadium safety |
—
|
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: official inquiry into stadium safety | Statement: [1902 Ibrox disaster, ledToInquiry, official inquiry into stadium safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledToInquiry Context triple: [1902 Ibrox disaster, ledToInquiry, official inquiry into stadium safety]
-
A.
hasNearbyDiscovery
Indicates that one entity has a discovery located in close physical or spatial proximity to it.
-
B.
ringDiscoveryPrecedes
Indicates that the discovery of a ring occurs earlier in time than another specified event or discovery.
-
C.
ringDiscovery
Indicates that an entity discovers, finds, or becomes aware of a particular ring.
-
D.
ledFrom
Indicates that one entity served as the source or origin from which another entity was led or guided.
-
E.
canBondWith
Indicates that one entity has the capability or compatibility to form a bond or connection with another entity.
- 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.