Triple
T30621218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Despeñaperros Pass |
E779448
|
entity |
| Predicate | hasRoadEngineeringWorks |
P192222
|
FINISHED |
| Object | tunnels |
—
|
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: tunnels | Statement: [Despeñaperros Pass, hasRoadEngineeringWorks, tunnels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadEngineeringWorks Context triple: [Despeñaperros Pass, hasRoadEngineeringWorks, tunnels]
-
A.
hasRoadImprovementProject
Indicates that there is a planned, ongoing, or completed project aimed at improving or upgrading a road or roadway infrastructure between the related entities.
-
B.
roadConstruction
Indicates that construction work is being carried out on a road, typically involving building, repairing, or modifying the roadway infrastructure.
-
C.
hasRoadImprovements
Indicates that road-related enhancements, upgrades, or maintenance activities have been carried out or are planned for a given location or roadway segment.
-
D.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
E.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: April 29, 2026, 8:27 p.m.