Triple
T3317965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monona Terrace Community and Convention Center |
E69725
|
entity |
| Predicate | hasRooftopFeature |
P27105
|
FINISHED |
| Object | rooftop terrace |
—
|
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: rooftop terrace | Statement: [Monona Terrace Community and Convention Center, hasRooftopFeature, rooftop terrace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRooftopFeature Context triple: [Monona Terrace Community and Convention Center, hasRooftopFeature, rooftop terrace]
-
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.
hasTopFloorFeature
Indicates that a building’s top floor possesses a specific feature, attribute, or amenity.
-
D.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
-
E.
hasBalcony
Indicates that a building or dwelling includes a balcony as part of its structure or features.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb113cb6c8190989b06476f6015fd |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.