Triple
T21245877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Александр Миротворец |
E523605
|
entity |
| Predicate | структура |
P81514
|
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.
structureFunction
Indicates that one entity’s physical or organizational structure serves a particular function or role in relation to another entity.
-
B.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
C.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
-
D.
featuresStructure
chosen
Indicates that one entity possesses, exhibits, or incorporates a particular structure as a notable characteristic or component.
-
E.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73599e5548190ad70d2c2bfa9e919 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:49 p.m.