Triple
T10188060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raid on Scarborough, Hartlepool and Whitby |
E236960
|
entity |
| Predicate | forceUsed |
P1062
|
FINISHED |
| Object | German battlecruisers |
—
|
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: German battlecruisers | Statement: [Raid on Scarborough, Hartlepool and Whitby, forceUsed, German battlecruisers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceUsed Context triple: [Raid on Scarborough, Hartlepool and Whitby, forceUsed, German battlecruisers]
-
A.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
B.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
-
C.
forceType
chosen
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
D.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
-
E.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded7a7aac8190af8dcb8374e62d68 |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.