Triple
T21343861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woody Island |
E526274
|
entity |
| Predicate | hasCoastalDefenseMissiles |
P87792
|
FINISHED |
| Object | reported |
—
|
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: reported | Statement: [Woody Island, hasCoastalDefenseMissiles, reported]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalDefenseMissiles Context triple: [Woody Island, hasCoastalDefenseMissiles, reported]
-
A.
missileLaunchCapability
chosen
Indicates that an entity has the ability or functionality to launch missiles.
-
B.
hasBallisticMissileSubmarine
Indicates that an entity possesses or operates a submarine specifically designed to carry and launch ballistic missiles.
-
C.
coastalDefense
Indicates a defensive relationship in which structures, systems, or actions are used to protect a coastline or shore area from threats such as erosion, flooding, or attack.
-
D.
hasMissileDetectionSystem
Indicates that an entity is equipped with a system capable of detecting missiles.
-
E.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
- 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8a85274f481909e699b390bed9350 |
completed | April 22, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:44 p.m.