Triple
T18863788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuckerman Ravine Trail |
E461378
|
entity |
| Predicate | hasIntermediatePoint |
P30410
|
FINISHED |
| Object | Hermit Lake |
—
|
NE NERFINISHED |
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: Hermit Lake | Statement: [Tuckerman Ravine Trail, hasIntermediatePoint, Hermit Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntermediatePoint Context triple: [Tuckerman Ravine Trail, hasIntermediatePoint, Hermit Lake]
-
A.
hasIntermediate
Indicates that there exists one or more entities that serve as a middle or transitional step between two related entities or stages.
-
B.
hasIntermediateCity
Indicates that there is a city located between two other places along a route or connection.
-
C.
hasIntermediateStation
Indicates that a route, journey, or connection includes a station that lies between its starting point and its final destination.
-
D.
isIntermediateBetween
Indicates that one entity occupies a position or state that lies between two other entities in a sequence, range, or process.
-
E.
intermediateConnectionPoint
chosen
Indicates a point that serves as a non-final, in-between link or junction within a larger connection or path between entities.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a304d4819092f14b7932d01afe |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.