Triple
T30279025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvia–Estonia border |
E770033
|
entity |
| Predicate | borderMarkerType |
P142064
|
FINISHED |
| Object | numbered boundary stones |
—
|
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: numbered boundary stones | Statement: [Latvia–Estonia border, borderMarkerType, numbered boundary stones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderMarkerType Context triple: [Latvia–Estonia border, borderMarkerType, numbered boundary stones]
-
A.
hasBorderMarkerType
chosen
Indicates that a border marker possesses or is classified by a specific type or category of border marker.
-
B.
borderCharacteristic
Indicates that one entity specifies a property, feature, or quality of the border or boundary of another entity.
-
C.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
D.
borderColor
Indicates the color that forms the boundary or outline of an entity.
-
E.
marksBoundaryIn
Indicates that one entity serves as a boundary or delimiter within, or for a specific region or structure of, another entity.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: April 29, 2026, 7:45 p.m.