Triple
T24816434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utena County |
E620933
|
entity |
| Predicate | borderedByInternalRegion |
P10768
|
FINISHED |
| Object | Panevėžys County |
E423168
|
NE 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: Panevėžys County | Statement: [Utena County, borderedByInternalRegion, Panevėžys County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByInternalRegion Context triple: [Utena County, borderedByInternalRegion, Panevėžys County]
-
A.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
borderIsInternalTo
Indicates that the boundary or border of one entity lies entirely within the interior of another entity, without crossing or extending outside it.
-
C.
innerBoundaryRegion
Indicates that one region serves as the inner boundary or enclosed area within another region or geometric entity.
-
D.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
E.
borderRegionOf
chosen
Indicates that one region lies along, touches, or forms part of the boundary of another region.
- F. None of above.
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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a101c3e2aac8190b5eaf719e1923dd5 |
completed | May 22, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:02 a.m.