Triple
T8145786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Biesterfeld |
E190206
|
entity |
| Predicate | nobleRankInHierarchy |
P80950
|
FINISHED |
| Object | below margravine and above baroness |
—
|
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 margravine and above baroness | Statement: [Countess of Biesterfeld, nobleRankInHierarchy, below margravine and above baroness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleRankInHierarchy Context triple: [Countess of Biesterfeld, nobleRankInHierarchy, below margravine and above baroness]
-
A.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
B.
nobleRankInOrder
Indicates that an entity holds a specific noble rank at a particular position within an established order of nobility.
-
C.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
D.
nobleRankType
Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank system.
-
E.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4447dbc48190affb0f34f6c85f5a |
completed | March 31, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39d20e78819092ea9e04357be008 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:36 p.m.