Triple
T38043686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kupiškis |
E949557
|
entity |
| Predicate | hasEldershipCenterRole |
P81461
|
FINISHED |
| Object | Kupiškis Eldership |
—
|
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: Kupiškis Eldership | Statement: [Kupiškis, hasEldershipCenterRole, Kupiškis Eldership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEldershipCenterRole Context triple: [Kupiškis, hasEldershipCenterRole, Kupiškis Eldership]
-
A.
hasLocalGovernanceRole
chosen
Indicates that an entity holds an official position or responsibility within a local or municipal governing body.
-
B.
hasTempleDistrictRole
Indicates that an entity holds a specific role or function within a temple district.
-
C.
hasGoverningRole
Indicates that one entity holds an official position of authority, control, or governance over another entity or domain.
-
D.
isPillarOf
Indicates that one entity serves as a fundamental support, foundation, or mainstay for another entity, often crucial to its stability, success, or existence.
-
E.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:20 p.m.