Triple
T2310340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A682 |
E51940
|
entity |
| Predicate | hasRoadClassification |
P1019
|
FINISHED |
| Object | primary route |
—
|
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: primary route | Statement: [A682, hasRoadClassification, primary route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadClassification Context triple: [A682, hasRoadClassification, primary route]
-
A.
hasRoadConfiguration
Indicates that there exists a specific arrangement or layout of roads associated with or characterizing an entity.
-
B.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
C.
isPublicRoad
Indicates that a given road is officially designated and accessible for use by the general public.
-
D.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
E.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.