Triple
T35424459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vologodsky District |
E1023880
|
entity |
| Predicate | centerIsPartOfDistrict |
P182956
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Vologodsky District, centerIsPartOfDistrict, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerIsPartOfDistrict Context triple: [Vologodsky District, centerIsPartOfDistrict, no]
-
A.
occursInDistrict
Indicates that an event or activity takes place within the boundaries of a specific district.
-
B.
isInnerDistrictOf
Indicates that one district is geographically or administratively located within and subordinate to another, larger district.
-
C.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
-
D.
isInDistrictCapitalCity
Indicates that one entity is located within the capital city of a specified administrative district.
-
E.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
- F. None of above. chosen
Provenance (4 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795905ed88190a9c6573824a56ca9 |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.