Triple
T1563379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir George Pocock |
E33376
|
entity |
| Predicate | promotedToRearAdmiral |
P342
|
FINISHED |
| Object | 1755 |
—
|
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: 1755 | Statement: [Sir George Pocock, promotedToRearAdmiral, 1755]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedToRearAdmiral Context triple: [Sir George Pocock, promotedToRearAdmiral, 1755]
-
A.
notableNavalCommander
Indicates that the subject is recognized as a distinguished or historically significant commander in naval forces.
-
B.
militaryRank
chosen
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
C.
shipCommissionedAs
Indicates that a ship entered active service under a specific name or designation at the time of its commissioning.
-
D.
chiefOfStaff
Indicates that one entity serves as the chief of staff for another entity, typically managing operations and coordinating activities on its behalf.
-
E.
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.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.