Triple
T3502171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tower 2 |
E73993
|
entity |
| Predicate | hasSkybridgeLevel |
P16038
|
FINISHED |
| Object | 41 |
—
|
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: 41 | Statement: [Tower 2, hasSkybridgeLevel, 41]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkybridgeLevel Context triple: [Tower 2, hasSkybridgeLevel, 41]
-
A.
hasSkyBridgeLocation
Indicates that one entity is the location where a sky bridge is situated or connected.
-
B.
hasSkyBridgeLength
Indicates the length measurement of a sky bridge connecting two structures or areas.
-
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.
hasSkyway
Indicates that there is an elevated, usually enclosed walkway or bridge connecting two or more structures or areas.
-
E.
skybridgeFloors
chosen
Indicates a relationship where a skybridge physically connects two or more specific floors of buildings or structures.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbef47988190b5b3fe2e452b9ac8 |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.