Triple
T24262569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Taneycomo |
E604746
|
entity |
| Predicate | hasPublicAccessAreas |
P112457
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lake Taneycomo, hasPublicAccessAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicAccessAreas Context triple: [Lake Taneycomo, hasPublicAccessAreas, yes]
-
A.
hasPublicSpaces
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
B.
hasProtectedAreaAccess
Indicates that an entity is permitted to enter, use, or otherwise access a designated protected area under defined conditions.
-
C.
hasPartOpenToPublic
chosen
Indicates that some portion or component of an entity is accessible for use or visitation by the general public.
-
D.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
E.
accessArea
Indicates that an entity is permitted to enter, use, or interact with a specified physical or logical area.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c691eb08190b6fbda8f187d7427 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.