Triple
T31088810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archduke Maximilian of Austria |
E792324
|
entity |
| Predicate | monarchNameAsRulerOfMexico |
P32785
|
FINISHED |
| Object | Maximilian I |
—
|
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: Maximilian I | Statement: [Archduke Maximilian of Austria, monarchNameAsRulerOfMexico, Maximilian I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchNameAsRulerOfMexico Context triple: [Archduke Maximilian of Austria, monarchNameAsRulerOfMexico, Maximilian I]
-
A.
monarchName
chosen
Indicates the personal name or official regnal name of a monarch in the relationship.
-
B.
monarchFullName
Indicates the complete official name by which a monarch is formally identified.
-
C.
monarchOnEstablishment
Indicates that a particular monarch holds or held the position of head of state for a given establishment (such as a country, state, or institution).
-
D.
commonMonarchOf
Indicates that two or more entities share the same monarch as their head of state or ruling sovereign.
-
E.
monarchAssociatedWith
Indicates a relationship where a monarch has a notable connection or affiliation with another entity, such as a person, place, institution, or event.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 9:02 p.m.