Triple
T30279019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvia–Estonia border |
E770033
|
entity |
| Predicate | hasRailCrossings |
P84289
|
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: [Latvia–Estonia border, hasRailCrossings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailCrossings Context triple: [Latvia–Estonia border, hasRailCrossings, true]
-
A.
hasRailwayCrossing
chosen
Indicates that a location or route includes a point where a railway line and a road or path intersect, typically at the same level.
-
B.
hasMajorRailCrossing
Indicates that there is a significant railway crossing (such as a major rail line intersecting a road or another transport route) at or associated with the referenced location or entity.
-
C.
railCrossingBetween
Indicates that a railway crossing is located between two specified entities or locations, connecting or intersecting them.
-
D.
hasTransportationCrossings
Indicates that one location or route includes points where transportation paths (such as roads, railways, or walkways) intersect or cross over/under another feature.
-
E.
hasCrosswalks
Indicates that designated pedestrian crosswalks are present at or associated with the specified location or roadway segment.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 7:45 p.m.