Triple
T12428836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonne of Bohemia |
E296968
|
entity |
| Predicate | playedDynasticRoleIn |
P25666
|
FINISHED |
| Object | Franco-Bohemian relations |
—
|
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: Franco-Bohemian relations | Statement: [Bonne of Bohemia, playedDynasticRoleIn, Franco-Bohemian relations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedDynasticRoleIn Context triple: [Bonne of Bohemia, playedDynasticRoleIn, Franco-Bohemian relations]
-
A.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
B.
hasPortrayedRole
Indicates that an entity has performed or depicted a specific role or character, typically in a work such as a film, play, or television show.
-
C.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
D.
hasFamousNamesakeRole
Indicates that an entity has a role or position that shares its name with a well-known or historically notable person.
-
E.
dynasticRole
chosen
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.