Triple
T14799389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romania–Ukraine border |
E347865
|
entity |
| Predicate | landBoundaryLengthApproxKm |
P57957
|
FINISHED |
| Object | 600 |
—
|
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: 600 | Statement: [Romania–Ukraine border, landBoundaryLengthApproxKm, 600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landBoundaryLengthApproxKm Context triple: [Romania–Ukraine border, landBoundaryLengthApproxKm, 600]
-
A.
shareLandBorderLengthApproxKm
chosen
Indicates that two entities share a land border whose length is approximately the given number of kilometers.
-
B.
longestLandBorderWith
Indicates that two entities share a land border and that this border is the longest land border for at least one of the entities.
-
C.
hasBorderLengthWithCanada_km
Indicates the length, in kilometers, of the land or maritime border that an entity shares with Canada.
-
D.
countryBordering
Indicates that one country shares a land or maritime boundary directly with another country.
-
E.
countryBorderFeatureOf
Indicates that a geographical feature (such as a river, mountain range, or coastline) serves as or is part of the border of a country.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd62c36c81909c2993dc7d1a79ea |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.