Triple
T25596789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General der Infanterie |
E641676
|
entity |
| Predicate | NATOrankEquivalent |
P24247
|
FINISHED |
| Object | OF-8 |
—
|
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: OF-8 | Statement: [General der Infanterie, NATOrankEquivalent, OF-8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NATOrankEquivalent Context triple: [General der Infanterie, NATOrankEquivalent, OF-8]
-
A.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
B.
NATORankCode
chosen
Indicates the standardized NATO rank classification assigned to a military person or position within the alliance.
-
C.
natureOfRank
Indicates the type or character of a rank, specifying what kind of ranking or hierarchical status it represents.
-
D.
nationalRank
Indicates the position or standing of an entity within a ranking system at the national level.
-
E.
nationalRankingScope
Indicates that the ranking being referred to is evaluated at the national (country-wide) level rather than regional or local scopes.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a30ad081909c4acab2736475a1 |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:28 p.m.