Triple
T1918238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom Centre |
E40066
|
entity |
| Predicate | hasSkyBridgeLocation |
P33145
|
FINISHED |
| Object | near the top of the 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 tower | Statement: [Kingdom Centre, hasSkyBridgeLocation, near the top of the tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkyBridgeLocation Context triple: [Kingdom Centre, hasSkyBridgeLocation, near the top of the tower]
-
A.
hasSkyway
Indicates that there is an elevated, usually enclosed walkway or bridge connecting two or more structures or areas.
-
B.
hasFootbridge
Indicates that there exists a footbridge providing a pedestrian connection between the related entities.
-
C.
skybridgeHeight
Indicates the vertical distance or clearance between a skybridge and a reference surface (such as the ground or roadway) or between connected structures.
-
D.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
-
E.
hasNearbyBridge
Indicates that one entity is located close to a bridge associated with or relevant to 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2107fe48190bafff825f1f805ad |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1b180e481908bbe893d6ba6208b |
completed | March 7, 2026, 5:03 a.m. |
Created at: March 4, 2026, 7:35 p.m.