Triple
T30278992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvia–Estonia border |
E770033
|
entity |
| Predicate | hasLandBoundary |
P194992
|
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, hasLandBoundary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandBoundary Context triple: [Latvia–Estonia border, hasLandBoundary, true]
-
A.
isOnlyLandBorderBetween
Indicates that one entity serves as the sole land border connection between two other entities, with no additional land borders existing between them.
-
B.
isLandlockedExceptForRiverBoundary
Indicates that an entity has no coastline on seas or oceans, except for a boundary formed by a river that connects (directly or indirectly) to such waters.
-
C.
hasLandBorderWithSea
Indicates that an entity’s land area directly borders or touches a sea along its coastline.
-
D.
hasBoundaryUnit
Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
-
E.
hasLandCutOffBy
Indicates that one land area is separated or interrupted from another by an intervening feature or boundary.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: April 29, 2026, 7:45 p.m.