Triple
T31322680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jõgeva |
E798790
|
entity |
| Predicate | isLocalCentreFor |
P124169
|
FINISHED |
| Object | administration |
—
|
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: administration | Statement: [Jõgeva, isLocalCentreFor, administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocalCentreFor Context triple: [Jõgeva, isLocalCentreFor, administration]
-
A.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
-
B.
isRegionalServiceCentre
Indicates that an entity functions as a regional service center responsible for providing services or support to a defined geographic area.
-
C.
isCentreOf
Indicates that one entity serves as the central point, core, or focal location relative to another entity or context.
-
D.
isServiceCentreFor
Indicates that one entity functions as a service center that provides support, maintenance, or related services for another entity.
-
E.
isRuralCentreFor
chosen
Indicates that one place functions as a primary service, administrative, or community hub for a surrounding rural area.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 9:15 p.m.