Triple
T30279005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvia–Estonia border |
E770033
|
entity |
| Predicate | passesNearTwinTown |
P3945
|
FINISHED |
| Object | Valka–Valga |
—
|
NE NERFINISHED |
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: Valka–Valga | Statement: [Latvia–Estonia border, passesNearTwinTown, Valka–Valga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passesNearTwinTown Context triple: [Latvia–Estonia border, passesNearTwinTown, Valka–Valga]
-
A.
passesNearCity
chosen
Indicates that the path, route, or trajectory of one entity goes close to, but not necessarily through, a specified city.
-
B.
hasNearbyTown
Indicates that one location has a town situated close to it in geographic proximity.
-
C.
hasTwinTown
Indicates that two towns or cities are officially paired in a twinning relationship, typically for cultural, social, or economic exchange.
-
D.
twinTownInCountry
Indicates that a town’s twin or sister city relationship is specifically with a town located in the given country.
-
E.
passesCity
Indicates that a route, path, or journey goes through or traverses a particular city as part of its course.
- 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_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 7:45 p.m.