Triple
T1699167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavarian police |
E36728
|
entity |
| Predicate | resultOfAction |
P374
|
FINISHED |
| Object | failure of Beer Hall Putsch |
—
|
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: failure of Beer Hall Putsch | Statement: [Bavarian police, resultOfAction, failure of Beer Hall Putsch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfAction Context triple: [Bavarian police, resultOfAction, failure of Beer Hall Putsch]
-
A.
result
chosen
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
B.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
-
C.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
D.
resultDetermination
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
-
E.
missionOutcome
Indicates the result or consequence of a mission, specifying whether and how the mission’s objectives were achieved or failed.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf169da888190b3aa334752f1952b |
completed | March 6, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69aa61b8ce348190b46154af0b041ff0 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.