Triple
T37667442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action of 23 November 1939 |
E937858
|
entity |
| Predicate | combatantShipType |
P97528
|
FINISHED |
| Object | armed merchant cruiser |
—
|
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: armed merchant cruiser | Statement: [Action of 23 November 1939, combatantShipType, armed merchant cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantShipType Context triple: [Action of 23 November 1939, combatantShipType, armed merchant cruiser]
-
A.
isWarshipOf
Indicates that a given warship belongs to, is operated by, or is part of the naval forces of a specified country or organization.
-
B.
opponentShipClass
Indicates that one entity is the ship class of an opposing or enemy vessel relative to another entity.
-
C.
warshipTypeUsed
chosen
Indicates that a particular type or class of warship is employed or utilized in a given context, event, or operation.
-
D.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
E.
capturedShipType
Indicates that one entity has taken possession of another entity’s ship, specifying the type or category of the ship that was captured.
- 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:18 p.m.