Triple
T1829592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUAM Ukraine |
E40730
|
entity |
| Predicate | supportsReformOf |
P4888
|
FINISHED |
| Object | civilian security sector of Ukraine |
—
|
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: civilian security sector of Ukraine | Statement: [EUAM Ukraine, supportsReformOf, civilian security sector of Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReformOf Context triple: [EUAM Ukraine, supportsReformOf, civilian security sector of Ukraine]
-
A.
isPartOfReform
Indicates that an action, measure, or component belongs to, contributes to, or is included within a broader reform initiative or process.
-
B.
reform
chosen
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
C.
supportedLegislation
Indicates that an entity endorsed, promoted, or voted in favor of a particular piece of legislation.
-
D.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
E.
supportedAct
Indicates that one entity provided assistance, endorsement, or backing for a particular action or activity performed by another entity.
- 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb45402688190b9a535b14030c354 |
completed | March 7, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69abafd6a9948190ac2b2743db6f8f69 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:32 p.m.