Triple
T1196959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Lai massacre |
E25688
|
entity |
| Predicate | militaryOperationContext |
P10341
|
FINISHED |
| Object | Search and destroy mission |
—
|
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: Search and destroy mission | Statement: [My Lai massacre, militaryOperationContext, Search and destroy mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryOperationContext Context triple: [My Lai massacre, militaryOperationContext, Search and destroy mission]
-
A.
militaryContext
chosen
Indicates that the relationship or action occurs within a military setting, framework, or operational environment.
-
B.
fieldOfOperation
Indicates the domain, area, or scope within which an entity operates or carries out its primary activities.
-
C.
encirclementOperation
Indicates a military action in which forces maneuver to surround an opposing force, cutting off its escape routes and lines of support.
-
D.
offensiveOperation
Indicates an action or campaign in which a party actively initiates hostile or military measures against an opponent.
-
E.
defensiveOperation
Indicates actions or measures undertaken to protect, guard, or defend a target against threats or attacks.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9a305c819091513394f1b67784 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.