Triple
T38532770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Federation military ranks |
E923410
|
entity |
| Predicate | hasNavalOfficerRank |
P198889
|
FINISHED |
| Object | Ensign |
—
|
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: Ensign | Statement: [Russian Federation military ranks, hasNavalOfficerRank, Ensign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavalOfficerRank Context triple: [Russian Federation military ranks, hasNavalOfficerRank, Ensign]
-
A.
hasNavalRank
chosen
Indicates that one entity holds or is assigned a specific rank within a naval hierarchy or organization.
-
B.
hasNotableNavalRank
Indicates that an entity holds or has held a distinguished or significant rank within a naval organization.
-
C.
navalRankContext
Indicates the relationship between an entity and its naval rank within a specific organizational, temporal, or situational context.
-
D.
hasNavalRole
Indicates that an entity holds or is assigned a role, function, or duty within a naval or maritime context.
-
E.
hasGeneralOfficerRank
Indicates that an entity holds a military rank at the general officer level.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
Created at: May 3, 2026, 4:32 p.m.