Triple
T22558059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netherlands and Germany |
E557738
|
entity |
| Predicate | hasLandBorderLength |
P57957
|
FINISHED |
| Object | about 575 km |
—
|
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: about 575 km | Statement: [Netherlands and Germany, hasLandBorderLength, about 575 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandBorderLength Context triple: [Netherlands and Germany, hasLandBorderLength, about 575 km]
-
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.
maritimeBoundaryLengthApproxKm
Indicates the approximate length, measured in kilometers, of a state's maritime boundary or coastline.
-
D.
countryBordering
Indicates that one country shares a land or maritime boundary directly with another country.
-
E.
hasLandBorderWithSea
Indicates that an entity’s land area directly borders or touches a sea along its coastline.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7b06e08190b3ca82a783965942 |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.