Triple
T24115136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Madison |
E597487
|
entity |
| Predicate | summitConnectedBy |
P144832
|
FINISHED |
| Object | Osgood Trail |
—
|
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: Osgood Trail | Statement: [Mount Madison, summitConnectedBy, Osgood Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitConnectedBy Context triple: [Mount Madison, summitConnectedBy, Osgood Trail]
-
A.
hasSummitConnectionTo
chosen
Indicates a relationship where two entities are connected through a shared summit, peak, or highest point, such that one has a direct summit-related linkage to the other.
-
B.
summitUsedBy
Indicates that a particular summit is utilized or accessed by a specified entity (such as a person, group, or organization).
-
C.
summitCount
Indicates the number of summits or peak ascents associated with an entity.
-
D.
summitStatus
Indicates the current state or outcome of a summit event, such as whether it is planned, ongoing, completed, or canceled.
-
E.
summitRepresents
Indicates that a summit serves as a formal venue or occasion in which certain positions, interests, or entities are presented, symbolized, or spoken for.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de1daf0481908767902bdf4e3682 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:04 p.m.