Triple
T35055150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivano-Frankivsk Raion |
E1011440
|
entity |
| Predicate | previouslyIncludedTerritoriesOf |
P131869
|
FINISHED |
| Object | Bohorodchany Raion |
—
|
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: Bohorodchany Raion | Statement: [Ivano-Frankivsk Raion, previouslyIncludedTerritoriesOf, Bohorodchany Raion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyIncludedTerritoriesOf Context triple: [Ivano-Frankivsk Raion, previouslyIncludedTerritoriesOf, Bohorodchany Raion]
-
A.
territoryOriginallyIncluded
chosen
Indicates that an earlier or original territorial boundary encompassed the referenced area or entity.
-
B.
includedTerritoryType
Indicates that one territory type is contained within, or forms part of, another territory type.
-
C.
territoryIncluded
Indicates that one territory is geographically or administratively contained within another territory.
-
D.
sometimesIncludesTerritory
Indicates that one entity occasionally, but not consistently, encompasses or contains the territory of another entity.
-
E.
expandedTerritoryOf
Indicates that one entity has increased or extended the geographic or jurisdictional area belonging to another entity.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:01 p.m.