Triple
T24897527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponsford Stand section |
E623185
|
entity |
| Predicate | isWithinStructure |
P157857
|
FINISHED |
| Object | Ponsford Stand |
—
|
NE NERFINISHED |
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: Ponsford Stand | Statement: [Ponsford Stand section, isWithinStructure, Ponsford Stand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWithinStructure Context triple: [Ponsford Stand section, isWithinStructure, Ponsford Stand]
-
A.
hasStructureOnOrAdjacent
Indicates that one entity has a physical structure located on it or immediately next to it.
-
B.
isStructureGroupOf
Indicates that one entity functions as the structural grouping or organizing framework that encompasses or defines the structure of another entity.
-
C.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
D.
indicatesStructure
Indicates that one entity specifies, defines, or reveals the structural organization or arrangement of another entity.
-
E.
isStruct
Indicates that an entity is a structured data type (such as a struct) rather than a primitive or other kind of type.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 5:26 a.m.