Triple
T14799390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romania–Ukraine border |
E347865
|
entity |
| Predicate | maritimeBoundaryLengthApproxKm |
P116153
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [Romania–Ukraine border, maritimeBoundaryLengthApproxKm, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeBoundaryLengthApproxKm Context triple: [Romania–Ukraine border, maritimeBoundaryLengthApproxKm, 100]
-
A.
hasCoastlineLengthRank
Indicates the relative position of an entity in an ordered ranking based on the length of its coastline.
-
B.
hasCoastlineLengthApprox
Indicates an approximate measurement of the total length of an entity’s coastline.
-
C.
shareLandBorderLengthApproxKm
Indicates that two entities share a land border whose length is approximately the given number of kilometers.
-
D.
hasLandBorderWithSea
Indicates that an entity’s land area directly borders or touches a sea along its coastline.
-
E.
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.
- 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_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. |
| PDg | Predicate description generation | batch_69de90c5e3a08190868680b081308c1d |
completed | April 14, 2026, 7:08 p.m. |
Created at: April 10, 2026, 1:31 a.m.