Triple
T25786465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union military operations |
E649429
|
entity |
| Predicate | firstOperation |
P58201
|
FINISHED |
| Object | Operation Concordia |
—
|
NE NERFINISHED |
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: Operation Concordia | Statement: [European Union military operations, firstOperation, Operation Concordia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOperation Context triple: [European Union military operations, firstOperation, Operation Concordia]
-
A.
firstPassOperation
Indicates that the related action or process occurs during the initial or primary pass of an operation or workflow.
-
B.
primaryOperation
chosen
Indicates the main or most important operation performed or used by an entity in a given context.
-
C.
firstLineInOperation
Indicates that one entity is the first line or initial step executed within a particular operation or process.
-
D.
firstUserOperation
Indicates that the referenced operation is the initial or earliest action performed by a given user.
-
E.
secondOperation
Indicates that an entity participates in or is associated with a subsequent or secondary operation relative to a primary one.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 22, 2026, 5:55 a.m.