Triple
T34683248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Militärstrukturen des Warschauer Paktes |
E890673
|
entity |
| Predicate | Instrument |
P119858
|
FINISHED |
| Object | gemeinsame Manöver |
—
|
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: gemeinsame Manöver | Statement: [Militärstrukturen des Warschauer Paktes, Instrument, gemeinsame Manöver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Instrument Context triple: [Militärstrukturen des Warschauer Paktes, Instrument, gemeinsame Manöver]
-
A.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
-
B.
typeOfInstrument
Indicates the specific kind or category of instrument associated with an entity.
-
C.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
D.
instruments
chosen
Indicates that an agent uses a tool, device, or means to carry out an action or achieve an effect.
-
E.
instrumentalIn
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:05 a.m.