Triple
T3301803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Stand SC |
E69350
|
entity |
| Predicate | standType |
P31102
|
FINISHED |
| Object | supporters section |
—
|
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: supporters section | Statement: [South Stand SC, standType, supporters section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standType Context triple: [South Stand SC, standType, supporters section]
-
A.
bandstandStyle
Indicates the architectural or design style characterizing a particular bandstand.
-
B.
hasStandsType
chosen
Indicates that an entity has or is associated with a particular type or category of stands (e.g., display stands, support stands, or similar structures).
-
C.
isFreeStanding
Indicates that an object or structure stands independently without needing external support or attachment.
-
D.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
E.
stationType
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a9450481909f0d630e5593085e |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.