Triple
T14319897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raglan Stand |
E355054
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Raglan Stand |
E355054
|
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: Raglan Stand | Statement: [Raglan Stand, hasName, Raglan Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raglan Stand Context triple: [Raglan Stand, hasName, Raglan Stand]
-
A.
Raglan Stand
chosen
Raglan Stand is a spectator seating section within Edgbaston Cricket Ground in Birmingham, England.
-
B.
Raglan
Raglan is a historic village in southeast Wales best known for the impressive late medieval Raglan Castle.
-
C.
Raglan
Raglan is a coastal town in New Zealand’s Waikato region, known for its surf beaches, arts community, and relaxed seaside atmosphere.
-
D.
Canton Stand
Canton Stand is a spectator seating section within Cardiff City Stadium, home of Cardiff City Football Club.
-
E.
Kippax Stand
Kippax Stand was a famous terrace and later all-seater stand at Manchester City's former Maine Road stadium, renowned for its passionate home support.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883bf71c8190a9a092a025cf98f0 |
completed | April 14, 2026, 6:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd468c4a7c8190951adb28e1d71365 |
completed | May 8, 2026, 2:12 a.m. |
Created at: April 10, 2026, 1:13 a.m.