Triple
T29678786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-17 shelling of Ellwood, California |
E750893
|
entity |
| Predicate | submarineDesignation |
P120324
|
FINISHED |
| Object | I-17 |
—
|
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: I-17 | Statement: [I-17 shelling of Ellwood, California, submarineDesignation, I-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: submarineDesignation Context triple: [I-17 shelling of Ellwood, California, submarineDesignation, I-17]
-
A.
submarineClassLeadShip
Indicates that one entity is the lead (first-built or first-commissioned) ship of a particular submarine class represented by the other entity.
-
B.
submarine
chosen
Indicates that one entity is a submarine in relation to another entity or context.
-
C.
submarineClassRole
Indicates the functional role or mission type assigned to a particular class of submarines within a naval context.
-
D.
submarineOnDisplay
Indicates that a submarine is being publicly exhibited, typically in a museum or similar display setting.
-
E.
primarySubmarineClassSupported
Indicates that an entity is designed to support, service, or operate primarily with a specific class of submarines.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6725f965c81909c66601bf11c5fdc |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:09 p.m.