Triple
T38532882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praporshchik |
E923412
|
entity |
| Predicate | rankSystemContext |
P58134
|
FINISHED |
| Object | distinct from commissioned officer corps |
—
|
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: distinct from commissioned officer corps | Statement: [Praporshchik, rankSystemContext, distinct from commissioned officer corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankSystemContext Context triple: [Praporshchik, rankSystemContext, distinct from commissioned officer corps]
-
A.
rankStatus
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
-
B.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
-
C.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
D.
hasRankContext
chosen
Indicates that an entity’s rank or ordering is defined, interpreted, or constrained within a specific contextual framework or situation.
-
E.
hadRankSystem
Indicates that an entity used or was governed by a particular ranking or rank classification system.
- 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_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.