Triple
T26321097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian high command |
E662110
|
entity |
| Predicate | introducedReforms |
P44089
|
FINISHED |
| Object | army organizational reforms after 1809 |
—
|
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: army organizational reforms after 1809 | Statement: [Austrian high command, introducedReforms, army organizational reforms after 1809]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedReforms Context triple: [Austrian high command, introducedReforms, army organizational reforms after 1809]
-
A.
implementedReformsIn
chosen
Indicates that an entity (typically a person, organization, or government) carried out or put into effect specific reforms within a particular context, domain, or location.
-
B.
notableReform
Indicates that an entity is recognized for having initiated, led, or been central to a significant reform or transformative change in a system, policy, or institution.
-
C.
typeOfReforms
Indicates the specific kinds or categories of reforms associated with an entity or situation.
-
D.
reformsBy
Indicates that one entity initiates, implements, or is responsible for changes or improvements (reforms) affecting another entity.
-
E.
advocatedReformOf
Indicates that one entity publicly supported or promoted changes to another entity, typically aiming to improve or modify its structure, policies, or practices.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 26, 2026, 10:28 p.m.