Triple
T31385183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockland County transportation network |
E800575
|
entity |
| Predicate | primaryRoadType |
P75679
|
FINISHED |
| Object | arterial 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: arterial roads | Statement: [Rockland County transportation network, primaryRoadType, arterial roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoadType Context triple: [Rockland County transportation network, primaryRoadType, arterial roads]
-
A.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
mainRoadInfrastructure
Indicates that a road segment functions as a primary or major route within the transportation infrastructure network.
-
C.
primaryHighwayComponent
Indicates that one entity serves as the main or principal highway component associated with another entity.
-
D.
isMainRoad
Indicates that a road serves as a primary or major thoroughfare within a transportation network.
-
E.
primaryRouteType
chosen
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:19 p.m.