Triple
T38532693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Russian military ranks |
E923409
|
entity |
| Predicate | topRankClass |
P104523
|
FINISHED |
| Object | 1st 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: 1st class | Statement: [Imperial Russian military ranks, topRankClass, 1st class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topRankClass Context triple: [Imperial Russian military ranks, topRankClass, 1st class]
-
A.
topClass
Indicates that an entity is the most general or highest-level class in a classification or hierarchy, with all other classes falling under it.
-
B.
classRank
Indicates the relative academic standing or position of an entity within a class or cohort based on performance or criteria.
-
C.
topClassOf
Indicates that one class is the most general or highest-level superclass from which another class (or set of classes) ultimately derives.
-
D.
highestRanking
chosen
Indicates that one entity holds the top or most senior rank relative to a set of other entities.
-
E.
rankingCategory
Indicates the classification or type of ranking under which an entity is evaluated or ordered.
- 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.