Triple
T22977630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mockingjay |
E571368
|
entity |
| Predicate | unexpectedConsequenceOf |
P150475
|
FINISHED |
| Object | Capitol’s use of jabberjays as spies |
—
|
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: Capitol’s use of jabberjays as spies | Statement: [Mockingjay, unexpectedConsequenceOf, Capitol’s use of jabberjays as spies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unexpectedConsequenceOf Context triple: [Mockingjay, unexpectedConsequenceOf, Capitol’s use of jabberjays as spies]
-
A.
avoidedConsequence
Indicates that an action or event prevented a particular consequence from occurring.
-
B.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
C.
announcedConsequence
Indicates that one entity has publicly stated or declared a specific outcome or consequence that will result from an action, event, or condition.
-
D.
consequenceInText
Indicates that one event, action, or state is presented in the text as a consequence or result of another.
-
E.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18292f3788190ab4e9d559e0070c8 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:48 p.m.