Triple
T23412011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poltava Uyezd |
E560094
|
entity |
| Predicate | administrativeRoleOfCenter |
P92979
|
FINISHED |
| Object | county seat |
—
|
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: county seat | Statement: [Poltava Uyezd, administrativeRoleOfCenter, county seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeRoleOfCenter Context triple: [Poltava Uyezd, administrativeRoleOfCenter, county seat]
-
A.
roleInAdministration
Indicates that an entity holds a specific position or function within an administrative structure or governing body.
-
B.
administrativeHeadquarter
Indicates the location that serves as the main administrative center or headquarters for an organization or governing body.
-
C.
isCentralAdministrativeBodyOf
Indicates that one entity serves as the main governing or coordinating administrative authority for another entity or system.
-
D.
roleInAdministrativeDivision
chosen
Indicates that an entity holds or fulfills a specific role, function, or position within a particular administrative division or jurisdiction.
-
E.
adminCenterLocatedOn
Indicates that the administrative center of an entity is situated on or within a specified geographic or physical feature.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a5124a54819087a7ae2f8a5b3dc0 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:38 p.m.