Triple
T18829070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act II of The Relapse |
E460472
|
entity |
| Predicate | hasNotableCharacterRole |
P20971
|
FINISHED |
| Object | Berinthia as witty intriguer |
—
|
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: Berinthia as witty intriguer | Statement: [Act II of The Relapse, hasNotableCharacterRole, Berinthia as witty intriguer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCharacterRole Context triple: [Act II of The Relapse, hasNotableCharacterRole, Berinthia as witty intriguer]
-
A.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
B.
notableWorkCharacter
Indicates that a character appears in, is associated with, or plays a role in a particular notable work.
-
C.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
-
D.
notableCharacterType
chosen
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
E.
hasFamousNamesakeRole
Indicates that an entity has a role or position that shares its name with a well-known or historically notable person.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99554848190933dd2810f5c810f |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.