Triple
T8909776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priestfield Stadium |
E212150
|
entity |
| Predicate | hasStand |
P6313
|
FINISHED |
| Object |
Medway Stand
Medway Stand is a principal spectator stand at Priestfield Stadium, home of Gillingham Football Club, providing seating and facilities for fans on match days.
|
E766622
|
NE FINISHED |
How this triple was built (4 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: Medway Stand | Statement: [Priestfield Stadium, hasStand, Medway Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Medway Stand Context triple: [Priestfield Stadium, hasStand, Medway Stand]
-
A.
South Stand
South Stand is a spectator seating section within Philips Stadion, the home ground of Dutch football club PSV Eindhoven.
-
B.
South Stand
South Stand is a spectator seating section located at New Douglas Park, the home stadium of Hamilton Academical FC in Scotland.
-
C.
South Stand
The South Stand is a spectator seating area at Rodney Parade stadium, used primarily for watching rugby and football matches.
-
D.
South Stand
South Stand is a spectator seating section located at the southern end of the Madejski Stadium, home to Reading Football Club.
-
E.
South Stand
South Stand is a spectator seating section within the Gtech Community Stadium, home to Brentford Football Club in London.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Medway Stand Triple: [Priestfield Stadium, hasStand, Medway Stand]
Generated description
Medway Stand is a principal spectator stand at Priestfield Stadium, home of Gillingham Football Club, providing seating and facilities for fans on match days.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Medway Stand Target entity description: Medway Stand is a principal spectator stand at Priestfield Stadium, home of Gillingham Football Club, providing seating and facilities for fans on match days.
-
A.
South Stand
South Stand is a spectator seating section within Philips Stadion, the home ground of Dutch football club PSV Eindhoven.
-
B.
South Stand
South Stand is a spectator seating section located at New Douglas Park, the home stadium of Hamilton Academical FC in Scotland.
-
C.
South Stand
The South Stand is a spectator seating area at Rodney Parade stadium, used primarily for watching rugby and football matches.
-
D.
South Stand
South Stand is a spectator seating section located at the southern end of the Madejski Stadium, home to Reading Football Club.
-
E.
South Stand
South Stand is a spectator seating section within the Gtech Community Stadium, home to Brentford Football Club in London.
- F. None of above. chosen
Provenance (5 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65227d008190b13ba162d0b3c9d1 |
completed | April 1, 2026, 12:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba36f8cc8190ab57ddc99b7219d1 |
completed | April 3, 2026, 1:01 p.m. |
| NEDg | Description generation | batch_69cfbade9330819096d4b0eeacdad6da |
completed | April 3, 2026, 1:04 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cfbec2b8888190a0390168fdcef05f |
completed | April 3, 2026, 1:21 p.m. |
Created at: March 30, 2026, 6:55 p.m.