Triple
T34950570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terespol–Brest |
E1007979
|
entity |
| Predicate | roadRoute |
P5943
|
FINISHED |
| Object | European route E30 |
—
|
NE NERFINISHED |
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: European route E30 | Statement: [Terespol–Brest, roadRoute, European route E30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadRoute Context triple: [Terespol–Brest, roadRoute, European route E30]
-
A.
roadMode
Indicates the mode or type of transportation being used on a road within the described relationship or action.
-
B.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
C.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
D.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
E.
roadName
chosen
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782cd7f4c819099f01e462863be2f |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.