Triple
T30917242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riptide |
E787613
|
entity |
| Predicate | starsCharacterRelationshipType |
P38921
|
FINISHED |
| Object | troubled marriage |
—
|
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: troubled marriage | Statement: [Riptide, starsCharacterRelationshipType, troubled marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starsCharacterRelationshipType Context triple: [Riptide, starsCharacterRelationshipType, troubled marriage]
-
A.
characterActorRelationship
Indicates a relationship where an actor portrays or is associated with a specific character in a work.
-
B.
relationshipToCharacter
chosen
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
C.
relationshipCharacterizedAs
Indicates that one relationship is described, defined, or typified in terms of another specified characteristic or relational type.
-
D.
titleCharacterRelation
Indicates the relationship between a work’s title and a specific character it references or centers on.
-
E.
relatedCharacterType
Indicates that one character has a specified type of relationship or role in connection to another character.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692b307488190a155de7798ec22fe |
completed | May 3, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:51 p.m.