Triple
T6722726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibrox Stadium |
E153434
|
entity |
| Predicate | safetyRedevelopment |
P72885
|
FINISHED |
| Object | 1970s–1980s |
—
|
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: 1970s–1980s | Statement: [Ibrox Stadium, safetyRedevelopment, 1970s–1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyRedevelopment Context triple: [Ibrox Stadium, safetyRedevelopment, 1970s–1980s]
-
A.
redevelopmentFor
Indicates a relationship where one entity is intended, designated, or used for the redevelopment of another entity.
-
B.
redevelopmentProject
Indicates a project involving the renewal, improvement, or transformation of an existing area, structure, or infrastructure, typically replacing or upgrading what was previously there.
-
C.
partOfRedevelopmentOf
Indicates that something is a component or phase within a larger redevelopment project or process.
-
D.
redevelopmentTo
Indicates a transformation relationship where one entity is redeveloped, converted, or repurposed into another entity.
-
E.
reopenedAfterRedevelopment
Indicates that a place or facility was closed for redevelopment and subsequently opened again once the redevelopment was completed.
- 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d139d50c81908b19120f139deaa5 |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d11fab808190b18160ff3829fcc6 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:08 p.m.