Triple
T30862779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archduke Alexander of Austria |
E786106
|
entity |
| Predicate | belongsToNobleRank |
P186029
|
FINISHED |
| Object | archduke |
—
|
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: archduke | Statement: [Archduke Alexander of Austria, belongsToNobleRank, archduke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToNobleRank Context triple: [Archduke Alexander of Austria, belongsToNobleRank, archduke]
-
A.
associatedNobleRank
Indicates that an entity is linked to or holds a particular noble rank or title.
-
B.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
C.
nobleRankOf
chosen
Indicates that one entity holds a specific noble title or rank within a hierarchical nobility system.
-
D.
nobleRankGrantedBy
Indicates that a particular noble rank or title was formally conferred upon someone by a specific granting authority or person.
-
E.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 29, 2026, 8:47 p.m.