Triple
T37667462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action of 23 November 1939 |
E937858
|
entity |
| Predicate | GermanShipArmament |
P185474
|
FINISHED |
| Object | heavy naval guns |
—
|
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: heavy naval guns | Statement: [Action of 23 November 1939, GermanShipArmament, heavy naval guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GermanShipArmament Context triple: [Action of 23 November 1939, GermanShipArmament, heavy naval guns]
-
A.
GermanShipRole
Indicates that an entity serves in a specific role or capacity on or for a German ship.
-
B.
GermanShipFate
Indicates the ultimate outcome or disposition of a German ship, such as whether it was sunk, captured, scuttled, or otherwise ended its service.
-
C.
navalArmament
chosen
Indicates that one entity serves as the naval weaponry or sea-based military equipment of another entity.
-
D.
GermanShipUndamaged
Indicates that a German ship remains intact and has not sustained damage.
-
E.
plannedArmamentClass
Indicates that an entity is intended or designated to be equipped with a particular class or type of armament.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.