Triple
T31474546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taraclia District |
E802954
|
entity |
| Predicate | borderTypeWithUkraine |
P197984
|
FINISHED |
| Object | land border |
—
|
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: land border | Statement: [Taraclia District, borderTypeWithUkraine, land border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTypeWithUkraine Context triple: [Taraclia District, borderTypeWithUkraine, land border]
-
A.
borderTypeWithRussia
Indicates the type or nature of a geographic border that an entity shares with Russia.
-
B.
borderTypeWithJordan
Indicates the type or nature of the border that an entity shares with Jordan.
-
C.
borderTypeWithXenia
Indicates the type or nature of the border or boundary that an entity has in relation to Xenia.
-
D.
borderTypeWithMongolia
Indicates the specific nature or classification of the border that an entity shares with Mongolia.
-
E.
borderTypeWithTurkmenistan
Indicates the type or nature of the border relationship that an entity has with Turkmenistan.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
| PDg | Predicate description generation | batch_69fec00e5c1c819083d174bb4bc35f29 |
completed | May 9, 2026, 5:03 a.m. |
Created at: April 30, 2026, 9:28 p.m.