Triple
T10148030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberstleutnant |
E231753
|
entity |
| Predicate | payGradeInBundeswehr |
P7397
|
FINISHED |
| Object | A14 |
—
|
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: A14 | Statement: [Oberstleutnant, payGradeInBundeswehr, A14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payGradeInBundeswehr Context triple: [Oberstleutnant, payGradeInBundeswehr, A14]
-
A.
payGrade
chosen
Indicates the level or category of compensation assigned to an entity, typically reflecting its rank, role, or seniority in a pay structure.
-
B.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
C.
isMilitaryOrderGrade
Indicates that one entity is classified as a specific grade or level within a military order or honor system in relation to another entity.
-
D.
payGradeComparison
Indicates that the relative pay grade or salary level between two entities is being compared (e.g., one is higher, lower, or equal to the other).
-
E.
isMilitaryRank
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec011c24819089b456fc8b9ed80c |
completed | April 2, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:08 p.m.