Triple
T18400429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autopista Central |
E449977
|
entity |
| Predicate | hasElectronicTollGates |
P97049
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Autopista Central, hasElectronicTollGates, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectronicTollGates Context triple: [Autopista Central, hasElectronicTollGates, yes]
-
A.
supportsElectronicTollCollection
chosen
Indicates that an entity is capable of handling or is compatible with electronic toll collection systems for automated toll payment.
-
B.
hasTollBoothsAt
Indicates that toll booths are present at or associated with a particular location or segment of infrastructure.
-
C.
operatesTollSystem
Indicates that an entity is responsible for running and managing a toll collection system.
-
D.
typeOfTollSystem
Indicates the specific kind or category of toll collection system used in a given context.
-
E.
isTollFacilityOf
Indicates that a facility (such as a toll booth, plaza, or gantry) is part of, or used to collect tolls for, a specific toll road or toll transportation infrastructure.
- F. None of above.
Provenance (3 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e5194f2a8c8190afcd7db23e3795fb |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.