Triple
T18652958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodina Mat |
E455985
|
entity |
| Predicate | currentSymbolicContext |
P105000
|
FINISHED |
| Object | Ukrainian national identity |
—
|
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: Ukrainian national identity | Statement: [Rodina Mat, currentSymbolicContext, Ukrainian national identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentSymbolicContext Context triple: [Rodina Mat, currentSymbolicContext, Ukrainian national identity]
-
A.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be interpreted.
-
B.
symbolForCurrent
chosen
Indicates that something serves as the current or active symbolic representation of another entity or state.
-
C.
contextName
Indicates the specific contextual label or identifier under which an entity, event, or relation is defined or interpreted.
-
D.
contextType
Indicates the type or category of contextual information associated with an entity or event.
-
E.
systemContext
Indicates the contextual conditions, settings, or environment within which a system operates or an interaction occurs.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5501279d08190aeca36df89fee2b2 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.