Triple
T11856382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beatrice of Hohenstaufen |
E282048
|
entity |
| Predicate | title held |
P100941
|
FINISHED |
| Object | princess of Hohenstaufen |
—
|
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: princess of Hohenstaufen | Statement: [Beatrice of Hohenstaufen, title held, princess of Hohenstaufen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: title held Context triple: [Beatrice of Hohenstaufen, title held, princess of Hohenstaufen]
-
A.
titleHeldThrough
Indicates that an entity holds or possesses a title by means of, or via the intermediary of, another entity or mechanism.
-
B.
titleHeldAs
chosen
Indicates that an entity holds or possesses a specific title in a particular capacity or role.
-
C.
heldTitleUntil
Indicates that an entity possessed or held a specific title or position continuously up to a particular end date or point in time.
-
D.
titleHeldIn
Indicates that a particular title or position is held within a specified organization, jurisdiction, or contextual domain.
-
E.
titleHeldAfter
Indicates that one entity held a particular title or position after another entity, establishing a temporal succession in holding that title.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a699089c8190b7a298baf13dcded |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.