Triple
T38538919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Остров Возрождения |
E924774
|
entity |
| Predicate | имелСтатус |
P154965
|
FINISHED |
| Object | закрытая военная зона |
—
|
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: закрытая военная зона | Statement: [Остров Возрождения, имелСтатус, закрытая военная зона]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имелСтатус Context triple: [Остров Возрождения, имелСтатус, закрытая военная зона]
-
A.
имелаСтатус
chosen
Indicates that an entity possessed or held a particular status during a certain period or context.
-
B.
hasFinancialStatus
Indicates that an entity possesses or is characterized by a particular financial condition, standing, or level of economic well-being.
-
C.
statusOfHolder
Indicates the current condition, role, or standing associated with the entity that holds or possesses something.
-
D.
addresseeStatus
Indicates the role, condition, or state of the entity that is the recipient or target of a communication or action.
-
E.
bankStatus
Indicates the current operational or financial condition of a bank, such as whether it is active, suspended, solvent, or insolvent.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd2e930608190b2b2af0d4753d7f0 |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.