Triple
T30212199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magna Mater Austriae |
E768096
|
entity |
| Predicate | historicallyPromotedBy |
P174706
|
FINISHED |
| Object | Habsburg monarchy |
—
|
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: Habsburg monarchy | Statement: [Magna Mater Austriae, historicallyPromotedBy, Habsburg monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyPromotedBy Context triple: [Magna Mater Austriae, historicallyPromotedBy, Habsburg monarchy]
-
A.
hasBeenPromotedBy
Indicates that one entity has received a promotion as a result of the decision or action taken by another entity.
-
B.
historicallyBackedBy
Indicates that something is supported, justified, or validated by historical evidence, records, or precedent.
-
C.
promotedFrom
Indicates that an entity has advanced to a new position, role, or status from a specified prior one.
-
D.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
E.
promotedVia
chosen
Indicates that something was advanced, advertised, or made more widely known through a particular channel, method, or medium.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: April 29, 2026, 7:33 p.m.