Triple
T10923836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-Scharführer |
E258012
|
entity |
| Predicate | parallelRankInSA |
P1944
|
FINISHED |
| Object | SA-Scharführer |
—
|
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: SA-Scharführer | Statement: [SS-Scharführer, parallelRankInSA, SA-Scharführer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelRankInSA Context triple: [SS-Scharführer, parallelRankInSA, SA-Scharführer]
-
A.
springRank
Indicates a ranking relationship where entities are ordered or positioned relative to each other based on a spring-like or force-directed hierarchy or influence measure.
-
B.
rankedAs
chosen
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
C.
canonicalRank
Indicates the standard or officially recognized rank or level assigned to an entity within an ordered hierarchy.
-
D.
hasRankingAlgorithm
Indicates that an entity uses or is associated with a specific algorithm for ranking or ordering items.
-
E.
hasApproximateRanking
Indicates that one entity is assigned a non-exact, estimated, or relative position or order with respect to others.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7708e3fd881908da10f24a856364c |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.