Triple
T1676792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baling Talks |
E36247
|
entity |
| Predicate | armedConflictContext |
P12023
|
FINISHED |
| Object | communist insurgency in Malaya |
—
|
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: communist insurgency in Malaya | Statement: [Baling Talks, armedConflictContext, communist insurgency in Malaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedConflictContext Context triple: [Baling Talks, armedConflictContext, communist insurgency in Malaya]
-
A.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
B.
militaryConflictCovered
Indicates that one entity (such as a document, report, or media item) covers, describes, or reports on a specific military conflict involving another entity.
-
C.
militaryContext
Indicates that the relationship or action occurs within a military setting, framework, or operational environment.
-
D.
conflictContext
Indicates the situational background or circumstances within which a conflict between entities occurs or is interpreted.
-
E.
beganDuringConflict
chosen
Indicates that the action or relationship started while a specified conflict was ongoing.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.