Triple
T21558814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian state highway SS4 |
E531960
|
entity |
| Predicate | hasRoadCode |
P144239
|
FINISHED |
| Object | SS 4 |
—
|
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: SS 4 | Statement: [Italian state highway SS4, hasRoadCode, SS 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadCode Context triple: [Italian state highway SS4, hasRoadCode, SS 4]
-
A.
hasRoadNumberStatus
Indicates that a road or route is associated with a specific status regarding its assigned road number (e.g., active, reserved, retired, or provisional).
-
B.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
-
C.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
D.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
-
E.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e21c5c8190aa32795e41f1550e |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:29 p.m.