Triple
T32815835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennebec River Rail Trail |
E839286
|
entity |
| Predicate | hasAccessPointIn |
P93497
|
FINISHED |
| Object | downtown Augusta, Maine |
—
|
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: downtown Augusta, Maine | Statement: [Kennebec River Rail Trail, hasAccessPointIn, downtown Augusta, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessPointIn Context triple: [Kennebec River Rail Trail, hasAccessPointIn, downtown Augusta, Maine]
-
A.
hasAccessPointFrom
Indicates that an entity can be reached or entered from a specific access point.
-
B.
isAccessPointOf
Indicates that one entity serves as an access point or entry interface through which another entity can be reached, used, or connected to.
-
C.
hasTrailAccessPoint
chosen
Indicates that there is a specific access point or entrance connecting a location to a trail or pathway.
-
D.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
E.
isBorderAccessPoint
Indicates that a location serves as an official point where passage across a border between two regions or jurisdictions is permitted or controlled.
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1:15 a.m.