Triple
T22597301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Yellow Admiral |
E574714
|
entity |
| Predicate | seriesNumberInAubreyMaturin |
P148875
|
FINISHED |
| Object | 18 |
—
|
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: 18 | Statement: [The Yellow Admiral, seriesNumberInAubreyMaturin, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesNumberInAubreyMaturin Context triple: [The Yellow Admiral, seriesNumberInAubreyMaturin, 18]
-
A.
fateAsBonhommeRichard
Indicates that an entity’s fate or ultimate outcome is the same as that of the ship Bonhomme Richard (e.g., being lost, destroyed, or otherwise meeting a similar end).
-
B.
numberOfSails
Indicates the quantity of sails associated with an entity, such as a boat or ship.
-
C.
firstLordOfTheAdmiralty
Indicates that an entity holds or has held the position of First Lord of the Admiralty in relation to a governing body or navy.
-
D.
captainServedUnder
Indicates that one captain performed their service or held their position under the authority or command of another person.
-
E.
roleInFirstFleet
Indicates that an entity held a specific role or position within the First Fleet.
- 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_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. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 2:50 p.m.