Triple
T22596744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue at the Mizzen |
E574700
|
entity |
| Predicate | hasNavalRankOfProtagonist |
P136453
|
FINISHED |
| Object | Royal Navy captain |
—
|
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: Royal Navy captain | Statement: [Blue at the Mizzen, hasNavalRankOfProtagonist, Royal Navy captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavalRankOfProtagonist Context triple: [Blue at the Mizzen, hasNavalRankOfProtagonist, Royal Navy captain]
-
A.
hasNotableNavalRank
chosen
Indicates that an entity holds or has held a distinguished or significant rank within a naval organization.
-
B.
hasNavalRole
Indicates that an entity holds or is assigned a role, function, or duty within a naval or maritime context.
-
C.
navalRankContext
Indicates the relationship between an entity and its naval rank within a specific organizational, temporal, or situational context.
-
D.
roleAtTrafalgar
Indicates the specific role, position, or function an entity held during the Battle of Trafalgar.
-
E.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f16269a56881909bb5af0258150f93 |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:50 p.m.