Triple
T17722112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Stand |
E442363
|
entity |
| Predicate | isPermanentStructure |
P128725
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [West Stand, isPermanentStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPermanentStructure Context triple: [West Stand, isPermanentStructure, true]
-
A.
hasPermanentStructures
Indicates that one entity possesses or contains long-lasting, fixed physical structures associated with it.
-
B.
isEngineeredStructure
Indicates that something is a man-made or artificially constructed structure, typically designed and built through engineering processes.
-
C.
rebuiltAsPermanentStructure
Indicates that something previously temporary or provisional has been reconstructed or replaced as a lasting, permanent structure.
-
D.
isWoodenStructure
Indicates that the subject is a structure primarily made of wood or constructed using wooden components.
-
E.
isEngineeringStructureOf
Indicates that one entity serves as an engineering structure that is functionally or structurally associated with, or part of, another entity.
- F. None of above. chosen
Provenance (4 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47486438c8190abe27eb4eb2c6fdf |
completed | April 19, 2026, 6:21 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d018227c8190b6624a2199e765e8 |
completed | April 18, 2026, 6:40 p.m. |
Created at: April 10, 2026, 10:07 a.m.