Triple
T20510439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lithuania–Russia border |
E503542
|
entity |
| Predicate | isDemarcated |
P69943
|
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: [Lithuania–Russia border, isDemarcated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDemarcated Context triple: [Lithuania–Russia border, isDemarcated, true]
-
A.
wasDemarcatedBetween
Indicates that a boundary or dividing line was formally established separating one entity from another.
-
B.
hasDemarcationAuthority
Indicates that an entity possesses the formal power or right to define, set, or modify boundaries or divisions between areas, responsibilities, or categories.
-
C.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
-
D.
demarcationStatus
chosen
Indicates the current state or condition of how clearly and officially a boundary or division between entities is defined or marked.
-
E.
isFenced
Indicates that an entity is enclosed or surrounded by a fence or fencing structure.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dcab8248190992e6ada23e5f253 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.