Triple
T11051203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perry Hall Road |
E261253
|
entity |
| Predicate | hasRoadUsers |
P77660
|
FINISHED |
| Object | local traffic |
—
|
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 traffic | Statement: [Perry Hall Road, hasRoadUsers, local traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadUsers Context triple: [Perry Hall Road, hasRoadUsers, local traffic]
-
A.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
B.
usesPublicRoads
chosen
Indicates that an entity travels on, operates vehicles on, or otherwise makes use of publicly accessible roadways.
-
C.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
D.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
E.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798698bd88190aa97afd37f55e19f |
completed | April 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.