Triple
T35586029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galichsky District |
E1028358
|
entity |
| Predicate | hasCenterFunction |
P58138
|
FINISHED |
| Object | administrative center |
—
|
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: administrative center | Statement: [Galichsky District, hasCenterFunction, administrative center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCenterFunction Context triple: [Galichsky District, hasCenterFunction, administrative center]
-
A.
hasCenterFeature
Indicates that an entity possesses a specific feature or element located at its center.
-
B.
hasCenterIn
Indicates that something is located, based, or primarily focused within a specified central place or area.
-
C.
hasCenterType
Indicates that something is characterized by or assigned a specific type or category of center.
-
D.
hasCenterStatus
chosen
Indicates that an entity holds a designated central role, position, or status within a system, organization, or structure.
-
E.
hasActiveCenter
Indicates that an entity possesses a central component, site, or region that is currently active or functioning.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:04 p.m.