Triple
T8000902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Iron Duke |
E186244
|
entity |
| Predicate | roleAtJutland |
P80257
|
FINISHED |
| Object | flagship of Admiral Sir John Jellicoe |
—
|
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: flagship of Admiral Sir John Jellicoe | Statement: [HMS Iron Duke, roleAtJutland, flagship of Admiral Sir John Jellicoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtJutland Context triple: [HMS Iron Duke, roleAtJutland, flagship of Admiral Sir John Jellicoe]
-
A.
roleAtTrafalgar
Indicates the specific role, position, or function an entity held during the Battle of Trafalgar.
-
B.
roleAtWaterloo
Indicates the specific position, function, or capacity an entity held in relation to the Battle of Waterloo.
-
C.
roleAtLeyteGulf
Indicates the specific role or function an entity performed in the context of the Battle of Leyte Gulf.
-
D.
roleAtNormandy
Indicates the specific role, position, or function an entity held in the context of the Normandy event or setting.
-
E.
roleAtPearlHarbor
Indicates the specific role, position, or function an entity held in relation to the events at Pearl Harbor.
- F. None of above. chosen
Provenance (4 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c9cd06081908b62bb41e228c321 |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:17 p.m.