Triple
T20466043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European transit corridor |
E502051
|
entity |
| Predicate | mayIncludeMode |
P140197
|
FINISHED |
| Object | road transport |
—
|
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: road transport | Statement: [European transit corridor, mayIncludeMode, road transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludeMode Context triple: [European transit corridor, mayIncludeMode, road transport]
-
A.
mayIncludeFeature
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
B.
mayIncludeUnitType
Indicates that something is allowed to contain or be associated with a particular type of unit.
-
C.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
D.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
E.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696aa0794819082c9989b1f7e9f37 |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:33 a.m.