Triple
T7234970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fir Park |
E155198
|
entity |
| Predicate | hasStand |
P6313
|
FINISHED |
| Object | East Stand |
E581874
|
NE 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: East Stand | Statement: [Fir Park, hasStand, East Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: East Stand Context triple: [Fir Park, hasStand, East Stand]
-
A.
East Stand
The East Stand is one of the main spectator stands at Old Trafford stadium, providing seating and facilities for fans watching Manchester United home matches.
-
B.
East Stand
East Stand is a spectator seating section of Loftus Versfeld Stadium in Pretoria, South Africa, used for viewing rugby and football matches.
-
C.
East Stand
The East Stand is a major spectator stand at Elland Road stadium, home of Leeds United Football Club.
-
D.
East Stand
The East Stand was one of the main spectator stands at Tottenham Hotspur’s former home ground, White Hart Lane, providing seating and facilities for fans along the side of the pitch.
-
E.
East Stand
chosen
East Stand is a spectator seating section at Rugby Park stadium, providing views of the pitch from the eastern side.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea130e5c819087f74883760fe327 |
completed | March 27, 2026, 8:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7cc2d96588190bcf150cbfe4d015c |
completed | March 28, 2026, 12:40 p.m. |
Created at: March 27, 2026, 2:55 p.m.