Triple
T30279002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvia–Estonia border |
E770033
|
entity |
| Predicate | passesThroughRegion_Estonia |
P176020
|
FINISHED |
| Object | Pärnu County |
—
|
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: Pärnu County | Statement: [Latvia–Estonia border, passesThroughRegion_Estonia, Pärnu County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passesThroughRegion_Estonia Context triple: [Latvia–Estonia border, passesThroughRegion_Estonia, Pärnu County]
-
A.
EstoniaStatus
Indicates the status or condition currently associated with Estonia in a given context.
-
B.
passesThroughCountry
Indicates that a route, path, or object traverses or crosses within the boundaries of a specified country.
-
C.
areaRankingInEstonia
Indicates the relative position of something in a size-based ranking specifically within the context of Estonia.
-
D.
hasEuroregion
Indicates a relationship where a geographic or administrative entity is part of, or associated with, a specific Euroregion.
-
E.
isInBalticSeaRegion
Indicates that something is geographically located within, or closely associated with, the Baltic Sea region.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 29, 2026, 7:45 p.m.