Triple
T16173086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Célé Valley |
E392489
|
entity |
| Predicate | hasOutdoorInfrastructure |
P74338
|
FINISHED |
| Object | marked hiking trails |
—
|
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: marked hiking trails | Statement: [Célé Valley, hasOutdoorInfrastructure, marked hiking trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorInfrastructure Context triple: [Célé Valley, hasOutdoorInfrastructure, marked hiking trails]
-
A.
hasOutdoorSpaceType
Indicates the specific kind of outdoor area associated with an entity, such as a balcony, terrace, garden, or patio.
-
B.
isOutdoorFacility
Indicates that a facility is located outdoors or primarily functions in an open-air environment.
-
C.
hasOutdoorResource
chosen
Indicates that an entity is associated with, provides, or includes access to an outdoor resource or facility.
-
D.
hasOutdoorPlatforms
Indicates that an entity includes one or more platforms or boarding areas that are located outdoors rather than inside a building or covered structure.
-
E.
outdoorVenue
Indicates that an event, activity, or gathering takes place at a location situated outdoors rather than inside a building or enclosed structure.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb88c948190a1d8b5518694ad53 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.