Triple
T27700223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Saxe-Teschen |
E698406
|
entity |
| Predicate | heldMilitaryCommand |
P94220
|
FINISHED |
| Object | Austrian army |
—
|
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: Austrian army | Statement: [House of Saxe-Teschen, heldMilitaryCommand, Austrian army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldMilitaryCommand Context triple: [House of Saxe-Teschen, heldMilitaryCommand, Austrian army]
-
A.
hadMilitaryPost
chosen
Indicates that an entity held an official position or assignment within a military organization.
-
B.
hasMilitaryAuthority
Indicates that one entity possesses formal power or command to direct, control, or make decisions over the military activities or forces of another entity.
-
C.
isMilitaryCommand
Indicates that one entity holds formal military authority or command over another entity or group.
-
D.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
-
E.
militaryConflictOversaw
Indicates that one party had authoritative oversight or command responsibility over a military conflict involving another party.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635a29ff08190bfd246ccaf0ddb4e |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:56 p.m.