Triple
T27919291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astroland |
E706158
|
entity |
| Predicate | hadObservationTower |
P163774
|
FINISHED |
| Object | Astrotower |
—
|
NE NERFINISHED |
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: Astrotower | Statement: [Astroland, hadObservationTower, Astrotower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadObservationTower Context triple: [Astroland, hadObservationTower, Astrotower]
-
A.
isObservationTower
Indicates that something functions as an observation tower, serving primarily as a structure for viewing or monitoring an area from an elevated position.
-
B.
observationTowerBuiltIn
Indicates that an observation tower was constructed within or during a specific location or time period.
-
C.
hasObservationDeckAccess
Indicates that an entity is permitted to enter or use an observation deck.
-
D.
hasObservationDeckName
Indicates that an observation deck is associated with a specific name or title.
-
E.
towerObservationDeck
Indicates that an observation deck is located on or is part of a tower.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 6:55 p.m.