Triple
T24539678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erzherzogin von Österreich |
E607055
|
entity |
| Predicate | rankRelativeToEmperor |
P148206
|
FINISHED |
| Object | below Empress of Austria |
—
|
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: below Empress of Austria | Statement: [Erzherzogin von Österreich, rankRelativeToEmperor, below Empress of Austria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankRelativeToEmperor Context triple: [Erzherzogin von Österreich, rankRelativeToEmperor, below Empress of Austria]
-
A.
rankWithinImperialFamily
chosen
Indicates the hierarchical position an individual holds within an imperial family relative to other family members.
-
B.
positionInDynasty
Indicates the specific role or rank an individual holds within a particular dynasty’s internal hierarchy.
-
C.
monarchicRank
Indicates the hierarchical level or status an individual holds within a monarchical system of rule.
-
D.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
E.
namedForEmperor
Indicates that something (such as a place, object, or institution) is named in honor of a specific emperor.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:26 a.m.