Triple
T33168076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easton, New Hampshire |
E848947
|
entity |
| Predicate | transportationAccessType |
P147666
|
FINISHED |
| Object | rural roads |
—
|
LITERAL FINISHED |
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: rural roads | Statement: [Easton, New Hampshire, transportationAccessType, rural roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationAccessType Context triple: [Easton, New Hampshire, transportationAccessType, rural roads]
-
A.
transportAccessType
chosen
Indicates the type or mode of transportation access available or used in a given context.
-
B.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
-
C.
transportAccessBy
Indicates that one entity has access to or is served by a particular mode or means of transportation provided or enabled by another entity.
-
D.
transportAccessFrom
Indicates that one location or entity has transportation access originating from another specified location or source.
-
E.
hasMotorVehicleAccess
Indicates that an entity is permitted to use or operate a motor vehicle within a specified area, context, or under certain conditions.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
Created at: May 1, 2026, 1:28 a.m.