Triple
T26085026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svetozar Boroević |
E657954
|
entity |
| Predicate | militaryRankAtPeak |
P109148
|
FINISHED |
| Object | Field Marshal of Austria-Hungary |
—
|
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: Field Marshal of Austria-Hungary | Statement: [Svetozar Boroević, militaryRankAtPeak, Field Marshal of Austria-Hungary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRankAtPeak Context triple: [Svetozar Boroević, militaryRankAtPeak, Field Marshal of Austria-Hungary]
-
A.
militaryRankBeforeAccession
Indicates the military rank held by an individual prior to their accession to a particular office, position, or status.
-
B.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
C.
militaryRankDate
Indicates the date on which an entity attained, held, or was recorded with a particular military rank.
-
D.
hasGeneralOfficerRank
chosen
Indicates that an entity holds a military rank at the general officer level.
-
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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 26, 2026, 7:42 p.m.