Triple
T10491070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Союз нерушимый республик свободных |
E247417
|
entity |
| Predicate | имеетХарактеристику |
P274
|
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.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
B.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
C.
hasTradeCharacteristic
Indicates that an entity possesses a specific trade-related attribute, quality, or feature.
-
D.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
E.
hasRoleCharacteristic
Indicates that an entity possesses a specific characteristic, quality, or attribute associated with a particular role.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5097d61e08190952d4354ef1bce52 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:24 p.m.