Triple
T7435047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Generaloberst |
E171591
|
entity |
| Predicate | partOfRankStructure |
P36072
|
FINISHED |
| Object | Prussian-German 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: Prussian-German officer corps | Statement: [Generaloberst, partOfRankStructure, Prussian-German officer corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfRankStructure Context triple: [Generaloberst, partOfRankStructure, Prussian-German officer corps]
-
A.
typicallyHoldsRank
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
B.
rankWithinOrganization
Indicates the relative hierarchical position or level an entity holds within a specific organization.
-
C.
rankStructureIncludes
chosen
Indicates that a given rank structure contains or encompasses a specified rank or set of ranks within its hierarchy.
-
D.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
-
E.
isRank
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
- 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_69c68a64228c8190affaec2a8127ce7b |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f328cf6081908bea065639fd3620 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:13 p.m.