Triple
T249580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Paramount (Huntington, New York) |
E5112
|
entity |
| Predicate | indoorOrOutdoor |
P8552
|
FINISHED |
| Object | indoor venue |
—
|
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: indoor venue | Statement: [The Paramount (Huntington, New York), indoorOrOutdoor, indoor venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorOrOutdoor Context triple: [The Paramount (Huntington, New York), indoorOrOutdoor, indoor venue]
-
A.
isOutdoorFacility
Indicates that a facility is located outdoors or primarily functions in an open-air environment.
-
B.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
-
C.
interiorStyle
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
D.
amenity
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
-
E.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d3728f0819086214ccc2db2305a |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c036b54819090a101c4cbdbcff7 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.