Triple
T34513585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobbie |
E886087
|
entity |
| Predicate | relationshipToMainCharacters |
P38921
|
FINISHED |
| Object | romantic partner |
—
|
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: romantic partner | Statement: [Bobbie, relationshipToMainCharacters, romantic partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToMainCharacters Context triple: [Bobbie, relationshipToMainCharacters, romantic partner]
-
A.
relationshipToCharacter
chosen
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
B.
relatedCharacter
Indicates that one character has a specified relationship or association with another character.
-
C.
appearsAsChildOfMainCharacters
Indicates that an entity is depicted or presented as the child of the story’s main characters.
-
D.
relatedCharacterContext
Indicates a contextual relationship between characters, such as roles, interactions, or situational connections that link them within a specific narrative or setting.
-
E.
relativeOfMainCharacter
Indicates that one entity is a family member or relative of the main character entity.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.