Triple
T24569996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | convoy JW 55B |
E607907
|
entity |
| Predicate | commanderOfDistantCover |
P106689
|
FINISHED |
| Object | Admiral Bruce Fraser |
—
|
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: Admiral Bruce Fraser | Statement: [convoy JW 55B, commanderOfDistantCover, Admiral Bruce Fraser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderOfDistantCover Context triple: [convoy JW 55B, commanderOfDistantCover, Admiral Bruce Fraser]
-
A.
escortCommander
chosen
Indicates that one entity serves as the commanding officer responsible for leading or overseeing an escort force or mission involving another entity.
-
B.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
C.
sideCommander
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
-
D.
ScottishCommander
Indicates that an entity serves as a military commander who is Scottish or associated with Scotland.
-
E.
combatant2Commander
Indicates that a combatant serves under the authority or command of a specific commander.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a923635c819097ecac0c82ec5f29 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:28 a.m.