Triple
T18349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Containment |
E362
|
entity |
| Predicate | reliesOnInstrument |
P1419
|
FINISHED |
| Object | military alliances |
—
|
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: military alliances | Statement: [Containment, reliesOnInstrument, military alliances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reliesOnInstrument Context triple: [Containment, reliesOnInstrument, military alliances]
-
A.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
B.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
-
C.
typicalInstrumentation
Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
-
D.
hasNotableRecordingBy
Indicates that an entity (such as a work or composition) has a well-known or significant recording created or performed by a specified agent (such as an artist, ensemble, or label).
-
E.
signedInstrument
Indicates that an entity has formally signed or executed a specific document, contract, or other legal instrument.
- F. None of above. chosen
Provenance (4 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_69a240778d288190815c0052ebbbcc91 |
completed | Feb. 28, 2026, 1:10 a.m. |
| NER | Named-entity recognition | batch_69a246cbca108190a92478df126d9bf8 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a2464f61648190ac690044be194972 |
completed | Feb. 28, 2026, 1:35 a.m. |
| PDg | Predicate description generation | batch_69a246cb2904819085c13207565a1db2 |
completed | Feb. 28, 2026, 1:37 a.m. |
Created at: Feb. 28, 2026, 1:14 a.m.