Triple
T14235697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One New Change |
E352870
|
entity |
| Predicate | hasRooftopRestaurant |
P27105
|
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: [One New Change, hasRooftopRestaurant, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRooftopRestaurant Context triple: [One New Change, hasRooftopRestaurant, yes]
-
A.
hasRooftop
Indicates that one entity possesses or is equipped with a rooftop as a structural feature.
-
B.
hasRooftopSpace
chosen
Indicates that an entity includes or provides an accessible rooftop area intended for use or occupancy.
-
C.
hasRestaurant
Indicates that one entity possesses, operates, or contains a restaurant associated with it.
-
D.
hasRestaurantType
Indicates that an entity is associated with or classified as a particular type or category of restaurant.
-
E.
hasDiningFeature
Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62411c888190a154acd56fe3fcaf |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.