Triple
T25896795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shenzhen Stock Exchange building |
E652486
|
entity |
| Predicate | hasElevatedPodiumHeight |
P53989
|
FINISHED |
| Object | approximately 36 m above ground |
—
|
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: approximately 36 m above ground | Statement: [Shenzhen Stock Exchange building, hasElevatedPodiumHeight, approximately 36 m above ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElevatedPodiumHeight Context triple: [Shenzhen Stock Exchange building, hasElevatedPodiumHeight, approximately 36 m above ground]
-
A.
hasPodiumType
Indicates the specific type or category of podium associated with an entity.
-
B.
heightWithPedestal
Indicates the total vertical measurement of an object including the height of its supporting pedestal.
-
C.
podiums
Indicates that an entity finishes in a top-placed position (typically first, second, or third) in a competitive event.
-
D.
elevationOfHolder
Indicates the vertical distance or height of the holder relative to a reference level (such as ground or sea level).
-
E.
upperTierHeight
chosen
Indicates the vertical measurement or elevation of an upper tier relative to a reference level or structure.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603bb02288190b40cedbed5b9651d |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 8:23 a.m.