Triple
T24426080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia State Route 169 |
E615860
|
entity |
| Predicate | roadSystemLevel |
P155879
|
FINISHED |
| Object | state |
—
|
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: state | Statement: [Georgia State Route 169, roadSystemLevel, state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadSystemLevel Context triple: [Georgia State Route 169, roadSystemLevel, state]
-
A.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
B.
roadSystemRole
Indicates the specific functional role or responsibility an entity has within a road or transportation network system.
-
C.
roadAxis
Indicates a central reference line that defines the primary longitudinal direction or alignment of a road.
-
D.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
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. chosen
Provenance (4 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a7406481908b85f3befc8feeee |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f2915233c48190a181c8c1924e892c |
completed | April 29, 2026, 11:16 p.m. |
Created at: April 18, 2026, 2:15 a.m.