Triple
T34804369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kathleen Kelly |
E1003308
|
entity |
| Predicate | romanticCoupleWith |
P177260
|
FINISHED |
| Object | Joe Fox |
—
|
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: Joe Fox | Statement: [Kathleen Kelly, romanticCoupleWith, Joe Fox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticCoupleWith Context triple: [Kathleen Kelly, romanticCoupleWith, Joe Fox]
-
A.
romanticSceneWith
Indicates a scene or situation in which the two entities are engaged together in a romantic context or interaction.
-
B.
romanticRivalryWith
Indicates a mutual competitive relationship in which two entities vie for the romantic attention or affection of the same person.
-
C.
isRomanticLeadOf
chosen
Indicates that one entity serves as the primary romantic partner or love-interest counterpart to another entity within a narrative or story.
-
D.
couplesTo
Indicates that one entity is joined or linked to another in a way that allows interaction, transfer, or mutual influence between them.
-
E.
romanticMisunderstandingsWith
Indicates a situation where two entities experience confusion, misinterpretation, or mistaken beliefs about each other’s romantic feelings, intentions, or relationship status.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 3:59 p.m.