Triple
T5703957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. invasion of Cambodia (1970) |
E125736
|
entity |
| Predicate | expandedConflictTo |
P65678
|
FINISHED |
| Object | Cambodian territory |
—
|
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: Cambodian territory | Statement: [U.S. invasion of Cambodia (1970), expandedConflictTo, Cambodian territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedConflictTo Context triple: [U.S. invasion of Cambodia (1970), expandedConflictTo, Cambodian territory]
-
A.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
B.
raisedForConflict
Indicates that an issue, concern, or case has been formally brought up due to a conflict between parties or conditions.
-
C.
supportedConflict
Indicates that one party provided assistance, resources, or endorsement to a side involved in a conflict or dispute.
-
D.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
E.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c024585d14819098ec34fd5a858836 |
completed | March 22, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c023dfec6881909ee6189b874b4348 |
completed | March 22, 2026, 5:16 p.m. |
Created at: March 22, 2026, 3:45 p.m.