Triple
T33984956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azovsky District |
E871386
|
entity |
| Predicate | isNotAdministrativelyPartOf |
P1611
|
FINISHED |
| Object | Azov |
—
|
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: Azov | Statement: [Azovsky District, isNotAdministrativelyPartOf, Azov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotAdministrativelyPartOf Context triple: [Azovsky District, isNotAdministrativelyPartOf, Azov]
-
A.
isNotPartOf
chosen
Indicates that one entity does not belong to, is not contained within, and is not a component or member of another entity.
-
B.
isAdministrativeUnitWithin
Indicates that one administrative unit is geographically or jurisdictionally contained within another administrative unit.
-
C.
isAdministeredAsPartOf
Indicates that an action or treatment is given or carried out as a component within a larger procedure, regimen, or program.
-
D.
notSubordinateTo
Indicates that one entity is not in a lower-ranking, subordinate, or reporting position to another entity within a hierarchy or organizational structure.
-
E.
belongsToAdministrativeSystem
Indicates that one entity is part of, or under the jurisdiction of, a particular administrative system or framework.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:50 a.m.