Triple
T7767068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyde Park Village |
E178975
|
entity |
| Predicate | outdoorOrientation |
P8618
|
FINISHED |
| Object | open-air |
—
|
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: open-air | Statement: [Hyde Park Village, outdoorOrientation, open-air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outdoorOrientation Context triple: [Hyde Park Village, outdoorOrientation, open-air]
-
A.
outdoorSection
Indicates that one entity is a section, area, or portion that is located outdoors or in an open-air environment relative to another entity.
-
B.
isOutdoor
chosen
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
C.
hasOutdoorLocation
Indicates that an entity is associated with or possesses a specific outdoor place or setting.
-
D.
cliffOrientation
Indicates the directional facing or alignment of a cliff relative to a reference frame (e.g., compass direction or slope aspect).
-
E.
hasOutdoorFocus
Indicates a relationship where an entity is primarily concerned with, oriented toward, or specialized in outdoor environments, activities, or contexts.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c7043451bc8190a76ee066b779b7d7 |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:11 p.m.