Triple
T33088468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raid on Yarmouth (1914) |
E846707
|
entity |
| Predicate | coastAttacked |
P128594
|
FINISHED |
| Object | East coast of England |
—
|
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: East coast of England | Statement: [Raid on Yarmouth (1914), coastAttacked, East coast of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastAttacked Context triple: [Raid on Yarmouth (1914), coastAttacked, East coast of England]
-
A.
shipAttacked
Indicates that one ship has carried out an attack against another ship.
-
B.
countryAttacked
Indicates that one country has carried out an attack against another country.
-
C.
cityAttackedBy
Indicates that a city is the target of an attack carried out by a specified agent or force.
-
D.
attackedByVessel
chosen
Indicates that an entity is the target of an attack carried out by a vessel (such as a ship or boat).
-
E.
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.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:26 a.m.