Triple
T24471425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landing Zone Albany |
E617110
|
entity |
| Predicate | ambushBy |
P77747
|
FINISHED |
| Object | North Vietnamese Army forces |
E1433767
|
NE 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: North Vietnamese Army forces | Statement: [Landing Zone Albany, ambushBy, North Vietnamese Army forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ambushBy Context triple: [Landing Zone Albany, ambushBy, North Vietnamese Army forces]
-
A.
surpriseAttack
chosen
Indicates an aggressive action initiated unexpectedly against a target that is unprepared or unaware.
-
B.
plannedAttackWith
Indicates that one entity has prepared or organized an attack using or involving another entity as the means or instrument of that attack.
-
C.
plannedAttack
Indicates that an entity has intentionally prepared and organized an attack against a target.
-
D.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
E.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
- F. None of above.
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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29943e9cc81909f1742c778bf3587 |
completed | April 29, 2026, 11:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1032e3084481908d2c088d7afe03f8 |
completed | May 22, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.