Triple
T19322739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brangäne |
E483266
|
entity |
| Predicate | hasRelationshipToIsolde |
P95556
|
FINISHED |
| Object | servant |
—
|
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: servant | Statement: [Brangäne, hasRelationshipToIsolde, servant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationshipToIsolde Context triple: [Brangäne, hasRelationshipToIsolde, servant]
-
A.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
-
B.
hasRoyalConnection
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
-
C.
hasHeritageConnectionWith
Indicates a relationship where two entities are linked through shared, inherited, or culturally transmitted heritage or ancestry.
-
D.
relationshipToOdette
chosen
Indicates the specific familial, social, or interpersonal connection that an entity has with Odette.
-
E.
literaryRelationship
Indicates a relationship between entities that are connected through literature, such as authorship, influence, adaptation, or other text-based associations.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d8948948190b76a384041333509 |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.