Triple
T24067502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hereditary Prince of the Habsburg Monarchy |
E596130
|
entity |
| Predicate | typicalHolderRank |
P7007
|
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: [Hereditary Prince of the Habsburg Monarchy, typicalHolderRank, archduke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHolderRank Context triple: [Hereditary Prince of the Habsburg Monarchy, typicalHolderRank, archduke]
-
A.
typicallyHoldsRank
chosen
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
B.
lastHolderRank
Indicates the rank or position held by the most recent entity that possessed or held a given item, title, or role.
-
C.
titleHolderRank
Indicates the relative position or level of precedence assigned to a title holder within a ranked order or hierarchy.
-
D.
establishedRank
Indicates that a stable or officially recognized hierarchical position or level has been assigned to an entity relative to others.
-
E.
memberHeldRank
Indicates that a member possessed or occupied a specific rank or position within an organization or hierarchy.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da5c57e88190ba05cc41b8fd035a |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:40 p.m.