Triple
T18875467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrid–Valencia railway |
E461671
|
entity |
| Predicate | parallelInfrastructure |
P27565
|
FINISHED |
| Object | Madrid–Levante high-speed rail network |
—
|
NE NERFINISHED |
How this triple was built (3 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: Madrid–Levante high-speed rail network | Statement: [Madrid–Valencia railway, parallelInfrastructure, Madrid–Levante high-speed rail network]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Madrid–Levante high-speed rail network Context triple: [Madrid–Valencia railway, parallelInfrastructure, Madrid–Levante high-speed rail network]
-
A.
Madrid–Seville high-speed rail line
The Madrid–Seville high-speed rail line is a pioneering Spanish high-speed railway corridor that connects the capital Madrid with Seville in Andalusia and helped launch Spain’s modern AVE network.
-
B.
Madrid–Toledo high-speed rail line
The Madrid–Toledo high-speed rail line is a Spanish AVE route that connects the capital Madrid with the historic city of Toledo via dedicated high-speed tracks.
-
C.
Madrid–Barcelona high-speed line
The Madrid–Barcelona high-speed line is a major Spanish AVE railway corridor that connects the country’s capital with its second-largest city using dedicated high-speed infrastructure.
-
D.
Madrid–Valladolid high-speed line
The Madrid–Valladolid high-speed line is a major Spanish AVE railway corridor connecting Madrid with Valladolid as part of the country’s high-speed rail network.
-
E.
Madrid–Huesca high-speed rail line
The Madrid–Huesca high-speed rail line is a Spanish AVE route that connects Madrid with northeastern Aragon, forming part of the country’s core high-speed rail network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Madrid–Levante high-speed rail network Target entity description: The Madrid–Levante high-speed rail network is a Spanish high-speed railway system connecting Madrid with major cities in the Levante region, including Valencia and Alicante, as part of the AVE network.
-
A.
Madrid–Seville high-speed rail line
The Madrid–Seville high-speed rail line is a pioneering Spanish high-speed railway corridor that connects the capital Madrid with Seville in Andalusia and helped launch Spain’s modern AVE network.
-
B.
Madrid–Toledo high-speed rail line
The Madrid–Toledo high-speed rail line is a Spanish AVE route that connects the capital Madrid with the historic city of Toledo via dedicated high-speed tracks.
-
C.
Madrid–Barcelona high-speed line
The Madrid–Barcelona high-speed line is a major Spanish AVE railway corridor that connects the country’s capital with its second-largest city using dedicated high-speed infrastructure.
-
D.
Madrid–Valladolid high-speed line
The Madrid–Valladolid high-speed line is a major Spanish AVE railway corridor connecting Madrid with Valladolid as part of the country’s high-speed rail network.
-
E.
Madrid–Huesca high-speed rail line
The Madrid–Huesca high-speed rail line is a Spanish AVE route that connects Madrid with northeastern Aragon, forming part of the country’s core high-speed rail network.
- F. None of above. chosen
Provenance (2 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3ce07788190a179705eb1b6c824 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 10, 2026, 11:57 a.m.