Triple
T3093024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yokohama Landmark Tower |
E64526
|
entity |
| Predicate | hasHighSpeedElevators |
P45867
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Yokohama Landmark Tower, hasHighSpeedElevators, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighSpeedElevators Context triple: [Yokohama Landmark Tower, hasHighSpeedElevators, Yes]
-
A.
hasElevators
Indicates that one entity is equipped with or contains one or more elevators for vertical transportation.
-
B.
hasEscalators
Indicates that one entity is equipped with or contains escalators that can be used for movement between different levels or areas.
-
C.
numberOfElevators
Indicates the total count of elevators associated with a given entity or location.
-
D.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
E.
hasLowerFloor
Indicates that one location, structure, or level includes or is directly connected to a floor situated below another floor.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada21055b88190b602425a513af7e6 |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.