Triple
T30197092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E74 |
E767662
|
entity |
| Predicate | hasRoadNumberInItaly |
P191095
|
FINISHED |
| Object | SS20 |
—
|
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: SS20 | Statement: [European route E74, hasRoadNumberInItaly, SS20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadNumberInItaly Context triple: [European route E74, hasRoadNumberInItaly, SS20]
-
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.
hasRoadNumberInFrance
Indicates that a road or route is assigned a specific official road number within the French road numbering system.
-
C.
hasRoadNumberContext
Indicates that a road number is associated with and contextualized by a specific road or route designation.
-
D.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
E.
hasRoadNumberSystem
Indicates that a place or region uses a specific system for assigning numbers to its roads or highways.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: April 29, 2026, 7:30 p.m.