Triple
T31616873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General James Mattoon Scott |
E806780
|
entity |
| Predicate | plansOperation |
P14398
|
FINISHED |
| Object | secret military takeover of the U.S. government |
—
|
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: secret military takeover of the U.S. government | Statement: [General James Mattoon Scott, plansOperation, secret military takeover of the U.S. government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansOperation Context triple: [General James Mattoon Scott, plansOperation, secret military takeover of the U.S. government]
-
A.
planNumber
Indicates that an entity is associated with a specific plan identifier or code used to distinguish it from other plans.
-
B.
operatorPlanned
Indicates that an operator has scheduled or arranged a specific action, process, or operation to occur.
-
C.
planOutcome
Indicates the result or consequence that is expected or produced by a given plan.
-
D.
programOperation
Indicates an operation or action performed by, within, or upon a program in a computational or procedural context.
-
E.
plan
chosen
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8aac01c8190bd3ae7bb98512259 |
completed | May 3, 2026, 1:45 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:39 p.m.