Triple
T3732928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleeping Giant |
E79110
|
entity |
| Predicate | topAccessibleBy |
P1985
|
FINISHED |
| Object | hiking trail |
—
|
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 trail | Statement: [Sleeping Giant, topAccessibleBy, hiking trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topAccessibleBy Context triple: [Sleeping Giant, topAccessibleBy, hiking trail]
-
A.
accessibleFrom
chosen
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
B.
accessibleAs
Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
-
C.
accessibleOn
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
-
D.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
E.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb2277a48190ae7594c4c4965a01 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.