Triple
T25708722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkspolizei |
E644669
|
entity |
| Predicate | hadRankStructureSimilarTo |
P6057
|
FINISHED |
| Object | military ranks |
—
|
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: military ranks | Statement: [Volkspolizei, hadRankStructureSimilarTo, military ranks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRankStructureSimilarTo Context triple: [Volkspolizei, hadRankStructureSimilarTo, military ranks]
-
A.
usesRankStructureSimilarTo
chosen
Indicates that one entity organizes or orders its elements according to a ranking system that is similar to the ranking system used by another entity.
-
B.
usesRankStructure
Indicates that an entity organizes its members or components according to a defined hierarchical rank structure.
-
C.
hadRankStructureReformedIn
Indicates that an entity’s rank structure was reorganized, modified, or reformed during a specified time or in a specified context.
-
D.
hasSimilarityTo
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc1385c4819082eff6432380dd2c |
completed | May 2, 2026, 1:28 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 9:08 p.m.