Triple
T2489601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Vian |
E52006
|
entity |
| Predicate | militaryRankAtEvent |
P9463
|
FINISHED |
| Object | Captain during the Altmark incident |
—
|
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: Captain during the Altmark incident | Statement: [Philip Vian, militaryRankAtEvent, Captain during the Altmark incident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRankAtEvent Context triple: [Philip Vian, militaryRankAtEvent, Captain during the Altmark incident]
-
A.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
B.
ageAtEnlistment
Indicates the age a person was when they enlisted in a service, organization, or role.
-
C.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
-
D.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
E.
hasMilitarySignificanceSince
Indicates that something has held military importance or strategic value starting from a specified point in time.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd17b7a048190bcc8f0a66514a052 |
completed | March 7, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.