Triple
T38575906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convoy MW10 |
E929399
|
entity |
| Predicate | underHeavyAttack |
P195803
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Convoy MW10, underHeavyAttack, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underHeavyAttack Context triple: [Convoy MW10, underHeavyAttack, true]
-
A.
forceAttacked
Indicates that one entity carried out an attack against another entity using force or coercive power.
-
B.
tookHeavyDamageAt
Indicates that an entity experienced severe or substantial damage at a specific location or point in time.
-
C.
attackValue
Indicates the offensive strength or damage potential an entity can inflict in an interaction or combat scenario.
-
D.
attackOnYourTurn
Indicates that the action of attacking occurs during the subject’s own turn in the sequence of play or events.
-
E.
oftenAttackedBy
Indicates that an entity is frequently the target of attacks carried out by another entity.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69fde5d677b88190bc904e6df8617c18 |
completed | May 8, 2026, 1:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.