Triple
T18185359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teresa |
E435396
|
entity |
| Predicate | connectedToProtagonistAs |
P27138
|
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: [Teresa, connectedToProtagonistAs, romantic partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToProtagonistAs Context triple: [Teresa, connectedToProtagonistAs, romantic partner]
-
A.
hasProtagonistRelationship
chosen
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
-
B.
isFriendOfProtagonist
Indicates that one entity is a friend or close ally of the story’s main character.
-
C.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
D.
hasProtagonistFromSource
Indicates that a work’s main character originates from, or is derived from, a specified source (such as another work, franchise, or medium).
-
E.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffdccd881908da772db78b9d081 |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.