Triple
T1219120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tahoe Vista |
E26176
|
entity |
| Predicate | hasOutdoorFacility |
P5383
|
FINISHED |
| Object | public beach access points |
—
|
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: public beach access points | Statement: [Tahoe Vista, hasOutdoorFacility, public beach access points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorFacility Context triple: [Tahoe Vista, hasOutdoorFacility, public beach access points]
-
A.
isOutdoorFacility
Indicates that a facility is located outdoors or primarily functions in an open-air environment.
-
B.
hasRecreationFacility
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
-
C.
isOutdoor
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
D.
hasRecreationalArea
chosen
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
E.
hasSkiableArea
Indicates that an entity possesses an area of terrain that can be used for skiing.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be1d55a08190a138b2411a7c4376 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.