Triple
T8346985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A75 motorway |
E196064
|
entity |
| Predicate | tollFreeForMostSections |
P82212
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [A75 motorway, tollFreeForMostSections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tollFreeForMostSections Context triple: [A75 motorway, tollFreeForMostSections, true]
-
A.
hasTollFreeSection
Indicates that a route, road, or transportation facility includes at least one segment where no toll is charged for use.
-
B.
nonTollSection
Indicates that a road segment or section is not subject to toll charges for its use.
-
C.
tollExemption
Indicates that an entity is not required to pay a toll or fee that would normally be charged for using a particular route, facility, or service.
-
D.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
E.
hasTollVariant
Indicates that an entity has a version or instance that requires paying a toll or fee for use or access.
- 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_69ca82edd63c8190b876b8465464c5fa |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8013d81c81908da48466cffb3939 |
completed | March 31, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:58 p.m.