Triple
T10977950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fletcher Christian |
E259421
|
entity |
| Predicate | joinedRoyalNavy |
P96415
|
FINISHED |
| Object | circa 1783 |
—
|
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: circa 1783 | Statement: [Fletcher Christian, joinedRoyalNavy, circa 1783]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedRoyalNavy Context triple: [Fletcher Christian, joinedRoyalNavy, circa 1783]
-
A.
enteredRoyalNavyFrontlineService
Indicates that an entity began active duty or operational deployment in the frontline forces of the Royal Navy.
-
B.
joinedMerchantNavy
Indicates that an individual entered into service with the merchant navy as a member of its crew or personnel.
-
C.
intendedToReplaceInRoyalNavy
Indicates that one entity was planned or designated to take over the role, duties, or position of another entity within the Royal Navy.
-
D.
RoyalNavyDesignation
Indicates that an entity has been assigned an official designation or identifier by the Royal Navy.
-
E.
hadNavalInfantry
Indicates that a military force possessed or was supported by specialized naval infantry (marines) as part of its organization or operations.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771f6a9448190b3932ee801ae0da9 |
completed | April 9, 2026, 9:31 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.