Triple
T17478183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFO Restaurant |
E425590
|
entity |
| Predicate | elevatorFrom |
P87576
|
FINISHED |
| Object | bridge pylon base |
—
|
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: bridge pylon base | Statement: [UFO Restaurant, elevatorFrom, bridge pylon base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatorFrom Context triple: [UFO Restaurant, elevatorFrom, bridge pylon base]
-
A.
hasElevatorConnection
chosen
Indicates that there is a direct elevator-based connection or access route between two locations or entities.
-
B.
elevationFrom
Indicates a vertical distance relationship where one entity’s height or altitude is measured relative to another reference entity.
-
C.
hasElevators
Indicates that one entity is equipped with or contains one or more elevators for vertical transportation.
-
D.
boardingElevation
Indicates the elevation at which boarding occurs for a vehicle or transport facility, typically relative to a standard reference level.
-
E.
elevatorTopSpeed_m_per_s
Indicates the maximum speed, in meters per second, that an elevator can travel.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bd865081909b5f84405c40ff14 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.