Triple
T22354830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Utah (BB-31) |
E552623
|
entity |
| Predicate | WorldWarIRole |
P43732
|
FINISHED |
| Object | convoy escort in Atlantic |
—
|
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: convoy escort in Atlantic | Statement: [USS Utah (BB-31), WorldWarIRole, convoy escort in Atlantic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WorldWarIRole Context triple: [USS Utah (BB-31), WorldWarIRole, convoy escort in Atlantic]
-
A.
worldWarIIRole
Indicates the specific role, position, or function an entity had in relation to World War II.
-
B.
roleInWorldWarI
chosen
Indicates the specific function, position, or involvement an entity had during World War I.
-
C.
roleInWarOrConflict
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
D.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
E.
preWorldWarIIRole
Indicates the role, position, or function an entity held or performed prior to the onset of World War II.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157ceb2308190941f6507e605a612 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.