Triple
T1002125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallonia |
E21626
|
entity |
| Predicate | borderLengthWithFrance |
P19532
|
FINISHED |
| Object | longest international border of Belgium |
—
|
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: longest international border of Belgium | Statement: [Wallonia, borderLengthWithFrance, longest international border of Belgium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderLengthWithFrance Context triple: [Wallonia, borderLengthWithFrance, longest international border of Belgium]
-
A.
borderTownOnFrenchSide
Indicates that a town is located on the French side of a border shared with another country.
-
B.
longestLandBorderWith
chosen
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.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
hasBorderLengthWithUSA
Indicates that the length of the land or maritime border shared between a given country or region and the USA has a specified measurement.
-
E.
countryBordering
Indicates that one country shares a land or maritime boundary directly with another 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4fcbc04819098d2125518f62ae7 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b1f4f88190822598cfd2a0fd2b |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.