Triple
T15386404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coyote Tango |
E367926
|
entity |
| Predicate | defenseScope |
P25697
|
FINISHED |
| Object | Pacific coastal defense |
—
|
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: Pacific coastal defense | Statement: [Coyote Tango, defenseScope, Pacific coastal defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenseScope Context triple: [Coyote Tango, defenseScope, Pacific coastal defense]
-
A.
defenseIncludes
Indicates that a defense strategy, plan, or system contains or incorporates a particular component, measure, or element as part of it.
-
B.
defenseArea
chosen
Indicates a spatial region or zone that is designated for defensive protection or military/security defense activities.
-
C.
defense
Indicates an action or relationship in which an entity protects, guards, or resists against a threat, attack, or criticism from another entity.
-
D.
defenseControl
Indicates that one entity exercises authority over, manages, or directs the defensive capabilities or protective measures of another entity.
-
E.
defenseInfrastructure
Indicates the existence or involvement of physical or organizational structures and facilities that support defense or protective capabilities between the related entities.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e74ff70819094c1a85f51d6e228 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.