Triple
T25608482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conundrum Hot Springs |
E641977
|
entity |
| Predicate | reachableOnlyBy |
P158909
|
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: [Conundrum Hot Springs, reachableOnlyBy, hiking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachableOnlyBy Context triple: [Conundrum Hot Springs, reachableOnlyBy, hiking]
-
A.
knownOnlyThrough
Indicates that one entity is aware of or has information about another entity exclusively via a specific intermediary source or channel, and not through any direct or alternative means.
-
B.
knownOnlyBy
Indicates that a piece of information or fact is exclusively known by a specific entity and by no others.
-
C.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
D.
accessibleWithin
Indicates that one entity can be reached, used, or entered from within the spatial or contextual bounds of another entity.
-
E.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
- F. None of above. chosen
Provenance (4 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9e0d2e88190b51e1eded1627f94 |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 4:40 p.m.