Triple
T38424749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proclamation No. 1081 |
E903326
|
entity |
| Predicate | reasonCited |
P24494
|
FINISHED |
| Object | alleged communist insurgency |
—
|
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: alleged communist insurgency | Statement: [Proclamation No. 1081, reasonCited, alleged communist insurgency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonCited Context triple: [Proclamation No. 1081, reasonCited, alleged communist insurgency]
-
A.
statedReason
chosen
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
B.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
-
C.
originalReason
Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
-
D.
justificationUsedBy
Indicates that a particular justification is employed or relied upon by a given entity (such as a person, system, or decision).
-
E.
reasonForPassage
Indicates the underlying cause, motivation, or purpose that explains why a particular passage or movement occurred.
- 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:31 p.m.