Triple
T33984933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azovsky District |
E871386
|
entity |
| Predicate | deFactoCenter |
P122397
|
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, deFactoCenter, Azov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deFactoCenter Context triple: [Azovsky District, deFactoCenter, Azov]
-
A.
deFactoFunction
Indicates that one entity effectively serves or operates in the role or capacity of another entity, even if not formally or officially designated as such.
-
B.
deFactoLimitedBy
Indicates that one entity’s actual functioning, scope, or effect is practically constrained or restricted by another entity, even if not formally or legally specified.
-
C.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
D.
deFactoCountry
Indicates that an entity functions as a country in practice (exercises governmental control and autonomy) even if it lacks full formal or legal recognition as a sovereign state.
-
E.
formsCenterOf
chosen
Indicates that one entity constitutes the central or core part of 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.