Triple
T3132994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yokohama Marine Tower |
E65458
|
entity |
| Predicate | isObservationTower |
P45559
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yokohama Marine Tower, isObservationTower, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isObservationTower Context triple: [Yokohama Marine Tower, isObservationTower, true]
-
A.
hasObservationDeckAccess
Indicates that an entity is permitted to enter or use an observation deck.
-
B.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
C.
towerLocation
Indicates that a tower is located at, or associated with, a specific place or geographic location.
-
D.
observationDeckHeight
Indicates the vertical distance of an observation deck above a reference level, typically the ground or sea level.
-
E.
observationPlatform
Indicates that one entity serves as the physical or virtual platform, site, or facility from which observations of another entity or phenomenon are made.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada56104ec8190a14591ed73f3fe83 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.