Triple
T38558742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comando Supremo |
E925315
|
entity |
| Predicate | coordinatedOperationsWith |
P435
|
FINISHED |
| Object | German armed forces |
—
|
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: German armed forces | Statement: [Comando Supremo, coordinatedOperationsWith, German armed forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatedOperationsWith Context triple: [Comando Supremo, coordinatedOperationsWith, German armed forces]
-
A.
coordinatesMilitaryOperationsOf
Indicates having authority to plan, direct, and manage the military operations carried out by another entity.
-
B.
coordinatedWith
chosen
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
C.
coordinatedUnder
Indicates that one entity is organized, directed, or managed under the authority or coordination of another entity.
-
D.
coordinateOperationWith
Indicates that one entity organizes and aligns its actions or processes with another entity to achieve a coordinated outcome.
-
E.
alliedOperation
Indicates that two or more entities are cooperating as allies in a shared operation or coordinated activity.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:32 p.m.