Triple
T10935807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IAI Dagger |
E258328
|
entity |
| Predicate | sawIntensiveCombatIn |
P38978
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [IAI Dagger, sawIntensiveCombatIn, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawIntensiveCombatIn Context triple: [IAI Dagger, sawIntensiveCombatIn, 1982]
-
A.
sawCombat
chosen
Indicates that an entity directly participated in active military or armed conflict.
-
B.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
C.
hasCombat
Indicates that an entity engages in, is involved with, or possesses the capability for combat or fighting interactions with other entities.
-
D.
sawCombatAfterWWII
Indicates that the entity participated in or experienced military combat operations occurring after the end of World War II.
-
E.
introducedToCombat
Indicates that something was brought into use or implemented specifically for the purpose of addressing or mitigating a particular problem, threat, or undesirable condition.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770afaa1c8190b8fced9c694c0938 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.