Triple
T19904141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuksachi Lodge |
E478366
|
entity |
| Predicate | offersActivityAccess |
P1983
|
FINISHED |
| Object | hiking |
—
|
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: hiking | Statement: [Wuksachi Lodge, offersActivityAccess, hiking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersActivityAccess Context triple: [Wuksachi Lodge, offersActivityAccess, hiking]
-
A.
offersActivity
chosen
Indicates that one entity provides or makes available a specific activity for another entity to participate in or use.
-
B.
offersAccess
Indicates that one entity provides another entity with the ability or permission to use, enter, or interact with a resource, service, or location.
-
C.
offersAccessVia
Indicates that one entity provides a means or channel through which another entity can be accessed or utilized.
-
D.
offersPass
Indicates that one entity provides or makes available a pass (such as a ticket, permit, or access credential) to another entity.
-
E.
offersEvent
Indicates that an entity provides or makes available a specific event.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65944c55481909b54a8f9a9c087d6 |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.