Triple
T38532695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Russian military ranks |
E923409
|
entity |
| Predicate | grantedNobilityFromClass |
P9679
|
FINISHED |
| Object | 8th class |
—
|
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: 8th class | Statement: [Imperial Russian military ranks, grantedNobilityFromClass, 8th class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedNobilityFromClass Context triple: [Imperial Russian military ranks, grantedNobilityFromClass, 8th class]
-
A.
nobleRankGrantedBy
Indicates that a particular noble rank or title was formally conferred upon someone by a specific granting authority or person.
-
B.
nobilityClass
chosen
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
C.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
D.
nobilitySystem
Indicates a social or political structure in which individuals are ranked by hereditary titles or noble status.
-
E.
positionOnNobility
Indicates the rank or status an entity holds within a hierarchy of nobility.
- 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_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 3, 2026, 4:32 p.m.