Triple
T31177180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viljandi Town Council |
E794781
|
entity |
| Predicate | isPartOfGovernmentSystemOf |
P13419
|
FINISHED |
| Object | Estonia |
—
|
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: Estonia | Statement: [Viljandi Town Council, isPartOfGovernmentSystemOf, Estonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfGovernmentSystemOf Context triple: [Viljandi Town Council, isPartOfGovernmentSystemOf, Estonia]
-
A.
isPartOfGovernment
chosen
Indicates that an entity belongs to, is included within, or functions as a component of a governmental body or system.
-
B.
basedInGovernmentType
Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
-
C.
typeOfGovernmentInstitution
Indicates that one entity is a government institution of the type or category specified by the other entity.
-
D.
governmentalUnit
Indicates that one entity functions as a governmental or administrative unit in relation to another entity.
-
E.
governsInPoliticalSystem
Indicates that one entity exercises authoritative control or rule over another entity within a specified political system or structure.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: April 29, 2026, 9:08 p.m.