Triple
T36162384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baiyoke Tower II |
E1045912
|
entity |
| Predicate | revolvingViewpointLevel |
P156597
|
FINISHED |
| Object | 84 |
—
|
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: 84 | Statement: [Baiyoke Tower II, revolvingViewpointLevel, 84]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revolvingViewpointLevel Context triple: [Baiyoke Tower II, revolvingViewpointLevel, 84]
-
A.
hasViewpointElevation
chosen
Indicates the vertical height or altitude of the viewpoint relative to a reference level (such as ground or sea level).
-
B.
hasViewingPointFor
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
-
C.
positionOnRevolution
Indicates the relative location or phase of an entity along its path during a revolution around another body or axis.
-
D.
viewpointNear
Indicates that one entity serves as a viewpoint or vantage location that is geographically close to another entity.
-
E.
viewpointFrom
Indicates a relationship where something is observed, depicted, or described from the perspective or location of a particular entity or point.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.