Triple
T35000604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavenly Finley |
E1009663
|
entity |
| Predicate | hasRomanticRelation |
P181372
|
FINISHED |
| Object | Chance Wayne |
—
|
NE NERFINISHED |
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: Chance Wayne | Statement: [Heavenly Finley, hasRomanticRelation, Chance Wayne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanticRelation Context triple: [Heavenly Finley, hasRomanticRelation, Chance Wayne]
-
A.
hasFictionalRomanticInterest
Indicates that one entity is portrayed as having a romantic attraction or interest toward another entity within a fictional context.
-
B.
hasRomanticTensionWith
Indicates a mutual or one-sided romantic attraction or unresolved romantic interest existing between two entities.
-
C.
romanticOrSexualPartners
chosen
Indicates that the entities have been, are, or are intended to be involved as romantic and/or sexual partners with each other.
-
D.
sexualRelationshipTo
Indicates that one entity has engaged in a sexual relationship or sexual activity with another entity.
-
E.
hasRomanticEntanglementInPlot
Indicates that a romantic relationship or involvement between characters is a significant element within the narrative plot.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:01 p.m.