Triple
T8453369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little York, New York |
E199854
|
entity |
| Predicate | hasRoadAccessType |
P55348
|
FINISHED |
| Object | local 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: local roads | Statement: [Little York, New York, hasRoadAccessType, local roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadAccessType Context triple: [Little York, New York, hasRoadAccessType, local roads]
-
A.
hasAccessRoadType
chosen
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
-
B.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
C.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
D.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
E.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe48aee388190864ef1186d5ee419 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.