Triple
T12922757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FASGW(H) anti-ship missiles |
E309164
|
entity |
| Predicate | engagementProfile |
P3663
|
FINISHED |
| Object | over-the-horizon attack |
—
|
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: over-the-horizon attack | Statement: [FASGW(H) anti-ship missiles, engagementProfile, over-the-horizon attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementProfile Context triple: [FASGW(H) anti-ship missiles, engagementProfile, over-the-horizon attack]
-
A.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
B.
engagementType
chosen
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
C.
engagementCapability
Indicates the ability or capacity of one entity to initiate, conduct, or sustain an interaction or engagement with another entity.
-
D.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
E.
engagementRole
Indicates the specific function, capacity, or responsibility an entity assumes within a particular engagement 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e7f6e881908c7bb12283898c80 |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.