Triple
T21320616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Albion |
E525601
|
entity |
| Predicate | roleAtNavarino |
P130445
|
FINISHED |
| Object | ship of the line in the allied fleet |
—
|
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: ship of the line in the allied fleet | Statement: [HMS Albion, roleAtNavarino, ship of the line in the allied fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtNavarino Context triple: [HMS Albion, roleAtNavarino, ship of the line in the allied fleet]
-
A.
roleInBattleOfNavarino
chosen
Indicates the specific role or involvement an entity had in the Battle of Navarino.
-
B.
roleAtTrafalgar
Indicates the specific role, position, or function an entity held during the Battle of Trafalgar.
-
C.
roleAtLeyteGulf
Indicates the specific role or function an entity performed in the context of the Battle of Leyte Gulf.
-
D.
roleAtBattleOfIquique
Indicates the specific role or function an entity held during the Battle of Iquique.
-
E.
hasNavalRole
Indicates that an entity holds or is assigned a role, function, or duty within a naval or maritime context.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ed0a2788190b6a71c8c720173dc |
completed | April 21, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:39 p.m.