Triple
T1400433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SkyPod |
E30767
|
entity |
| Predicate | positionRelativeToTower |
P27751
|
FINISHED |
| Object | near the top of the CN Tower |
—
|
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: near the top of the CN Tower | Statement: [SkyPod, positionRelativeToTower, near the top of the CN Tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToTower Context triple: [SkyPod, positionRelativeToTower, near the top of the CN Tower]
-
A.
turretPlacement
Indicates the spatial or positional relationship defining where a turret is placed relative to its environment or reference objects.
-
B.
relativeLocationOnIsland
Indicates a spatial relationship where one entity’s position is described relative to another entity specifically in the context of being on an island.
-
C.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
D.
positionRelativeToCoast
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
E.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c39c4c148190997150996ca26a99 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c13270d8819081d8ee1be34cabf5 |
completed | March 1, 2026, 10:44 p.m. |
Created at: March 1, 2026, 7:59 p.m.