Triple
T28154479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austro-Hungarian Army ranks |
E714704
|
entity |
| Predicate | officerRank |
P342
|
FINISHED |
| Object | Leutnant |
—
|
NE NERFINISHED |
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: Leutnant | Statement: [Austro-Hungarian Army ranks, officerRank, Leutnant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officerRank Context triple: [Austro-Hungarian Army ranks, officerRank, Leutnant]
-
A.
policeRank
Indicates that one entity holds a specific rank or position within a police organization relative to another entity.
-
B.
militaryRank
chosen
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
C.
civilServiceRank
Indicates that one entity holds a specific rank or position within a civil service hierarchy relative to another entity or classification.
-
D.
commissionedOfficerRank
Indicates that one entity holds a rank that qualifies them as a commissioned officer in a formal organizational hierarchy.
-
E.
officerCorps
Indicates that an entity belongs to, is part of, or is associated with a group or body of officers within an organization or institution.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 27, 2026, 10:01 p.m.