Triple
T25902019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greer Childs |
E652640
|
entity |
| Predicate | oneOfThreeLoversOf |
P84449
|
FINISHED |
| Object | Nola Darling |
—
|
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: Nola Darling | Statement: [Greer Childs, oneOfThreeLoversOf, Nola Darling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfThreeLoversOf Context triple: [Greer Childs, oneOfThreeLoversOf, Nola Darling]
-
A.
romanticTriangleInvolves
chosen
Indicates a romantic relationship structure in which three individuals are mutually or asymmetrically involved in overlapping romantic connections.
-
B.
rumoredLoverOf
Indicates that one entity is widely believed or speculated to be the romantic partner or lover of another entity, without confirmed evidence.
-
C.
spouseOrLover
Indicates a romantic partnership between two entities, whether formalized as a spouse or existing as a lover.
-
D.
hasFianceeOfSonAsLover
Indicates that a person is in a romantic or sexual relationship with their son’s fiancée.
-
E.
objectOfAffectionFor
Indicates that one entity is the target or recipient of another entity’s romantic or affectionate feelings.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 22, 2026, 8:26 a.m.