Triple
T28004027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Brigade |
E707224
|
entity |
| Predicate | locatedInStand |
P40
|
FINISHED |
| Object | North Curve at Celtic Park |
—
|
NE NERFINISHED |
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: North Curve at Celtic Park | Statement: [Green Brigade, locatedInStand, North Curve at Celtic Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInStand Context triple: [Green Brigade, locatedInStand, North Curve at Celtic Park]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
standsAt
Indicates that one entity is positioned upright at or near a specific location or reference point associated with another entity.
-
C.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
D.
stoodIn
Indicates that one entity was physically located within and occupying a place or area defined by another entity while in a standing position.
-
E.
locatedWith
Indicates that two or more entities are situated together in the same place or spatial context.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: April 27, 2026, 7:59 p.m.