Triple
T9025047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Заячий остров |
E216025
|
entity |
| Predicate | имеетСтатус |
P12717
|
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.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
B.
hasStatusLabel
chosen
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
C.
hasUnitStatus
Indicates that an entity is associated with a particular operational or condition status as a unit.
-
D.
hasUniqueStatus
Indicates that an entity possesses a status or condition that is distinct and not shared with any other entity in the given context.
-
E.
obtainedStatus
Indicates that an entity has received or achieved a particular status or condition as a result of some process or event.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7b902c81909fcbdc433a1acf7a |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.