Triple
T27430861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Flume |
E690631
|
entity |
| Predicate | liesAtSouthernEndOf |
P17679
|
FINISHED |
| Object | Franconia Range |
—
|
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: Franconia Range | Statement: [Mount Flume, liesAtSouthernEndOf, Franconia Range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesAtSouthernEndOf Context triple: [Mount Flume, liesAtSouthernEndOf, Franconia Range]
-
A.
locatedAtSouthernFootOf
Indicates that one entity is situated at the southern base or lower slope of another entity, typically a hill, mountain, or similar landform.
-
B.
isSouthernmostPartOf
chosen
Indicates that one entity is the geographically furthest south portion or section of another entity.
-
C.
hasSouthernTerminus
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
-
D.
southernmost
Indicates that one entity is located farther to the south than all other comparable entities in a given set or context.
-
E.
locatedSouthOf
Indicates that one entity is positioned geographically to the south of another entity.
- 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d59a6e88190a9042398d754c304 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:42 p.m.