Triple
T24525143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Jackson (New Hampshire) |
E606645
|
entity |
| Predicate | mainAccessTrail |
P3625
|
FINISHED |
| Object | Webster–Jackson 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: Webster–Jackson Trail | Statement: [Mount Jackson (New Hampshire), mainAccessTrail, Webster–Jackson Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAccessTrail Context triple: [Mount Jackson (New Hampshire), mainAccessTrail, Webster–Jackson Trail]
-
A.
mainAccessFor
Indicates that one entity serves as the primary means or route of access for another entity.
-
B.
trackAccess
Indicates that one entity monitors, records, or keeps a log of another entity’s access or usage of a resource.
-
C.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
-
D.
hasTrailAccessPoint
Indicates that there is a specific access point or entrance connecting a location to a trail or pathway.
-
E.
hasTrail
chosen
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
- 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.