Triple
T24749552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shayrat Airbase |
E619102
|
entity |
| Predicate | strikeLaunchedFrom |
P157704
|
FINISHED |
| Object | USS Porter |
—
|
NE NERFINISHED |
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: USS Porter | Statement: [Shayrat Airbase, strikeLaunchedFrom, USS Porter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strikeLaunchedFrom Context triple: [Shayrat Airbase, strikeLaunchedFrom, USS Porter]
-
A.
strikeLaunchedFrom
chosen
Indicates that a military or offensive strike was initiated or carried out starting from a specified origin location or platform.
-
B.
strikeAction
Indicates an action where one entity forcefully hits, attacks, or impacts another entity.
-
C.
typeOfStrike
Indicates the specific category or kind of strike involved in an event or action.
-
D.
battedBy
Indicates that an entity is the one who performed the batting action on another entity (e.g., a ball being batted by a player).
-
E.
firstStruck
Indicates that one entity was the initial party to hit, attack, or make physical contact with another in a conflict or interaction.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:24 a.m.