Triple
T16621819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichsarmee |
E403849
|
entity |
| Predicate | mobilizationRequires |
P115748
|
FINISHED |
| Object | Reichskrieg declaration |
—
|
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: Reichskrieg declaration | Statement: [Reichsarmee, mobilizationRequires, Reichskrieg declaration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobilizationRequires Context triple: [Reichsarmee, mobilizationRequires, Reichskrieg declaration]
-
A.
mobilizationUse
Indicates the use or deployment of resources, personnel, or assets as part of a mobilization effort.
-
B.
mobilization
Indicates the process by which entities are organized, activated, or assembled to take coordinated action or move into a state of readiness.
-
C.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
-
D.
mobilisationCondition
chosen
Indicates the circumstances or requirements under which an entity is activated, deployed, or put into operational use.
-
E.
canBeMobilisedFor
Indicates that an entity is capable of being called upon, activated, or deployed for a particular purpose, task, or operation.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754e80ec8190b3c66b33dbc7463c |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.