Triple
T38532716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Russian military ranks |
E923409
|
entity |
| Predicate | includedNavalRank |
—
|
GENERATED |
| Object | Admiral |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedNavalRank Context triple: [Imperial Russian military ranks, includedNavalRank, Admiral]
-
A.
hasNavalRank
chosen
Indicates that one entity holds or is assigned a specific rank within a naval hierarchy or organization.
-
B.
navalRankContext
Indicates the relationship between an entity and its naval rank within a specific organizational, temporal, or situational context.
-
C.
hasNotableNavalRank
Indicates that an entity holds or has held a distinguished or significant rank within a naval organization.
-
D.
equivalentRankInNavy
Indicates that two military positions are considered to have the same rank or level within their respective naval forces.
-
E.
navalHierarchyLevel
Indicates the relative rank or position of an entity within a naval command or organizational hierarchy.
- F. None of above.
Provenance (1 batch)
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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.