Triple
T19125403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | From Midshipman to Field Marshal |
E468163
|
entity |
| Predicate | depictsRankProgression |
P45510
|
FINISHED |
| Object | midshipman |
—
|
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: midshipman | Statement: [From Midshipman to Field Marshal, depictsRankProgression, midshipman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsRankProgression Context triple: [From Midshipman to Field Marshal, depictsRankProgression, midshipman]
-
A.
militaryRankProgression
chosen
Indicates the sequence or advancement of an individual’s positions within a structured military rank hierarchy.
-
B.
hasProgressionSystem
Indicates that an entity includes or is associated with a structured system through which progress, advancement, or development can occur over time.
-
C.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
-
D.
chronRank
Indicates the relative chronological order or ranking of events or time-related entities with respect to one another.
-
E.
promotedToRankBy
Indicates that an entity was elevated to a particular rank or position through the action or decision of another entity.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3cc5ba08190a1073f2836caf5d3 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.