Triple
T9824676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Hampshire Route 120 |
E238624
|
entity |
| Predicate | terminusIncludes |
P1866
|
FINISHED |
| Object | Hanover, New Hampshire |
—
|
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: Hanover, New Hampshire | Statement: [New Hampshire Route 120, terminusIncludes, Hanover, New Hampshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusIncludes Context triple: [New Hampshire Route 120, terminusIncludes, Hanover, New Hampshire]
-
A.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
B.
terminusType
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
C.
terminusFeature
Indicates that a specific physical or structural feature is located at, marks, or characterizes the endpoint or terminus of something.
-
D.
terminusNorth
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
-
E.
terminusCity
chosen
Indicates that a transportation route or service ends or has its final stop in a particular city.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3181c688190afea3b27ee392a30 |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:31 p.m.