Triple
T11301516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wade Kinsella |
E267601
|
entity |
| Predicate | hasLoveLifeCharacteristic |
P98395
|
FINISHED |
| Object | complicated love life |
—
|
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: complicated love life | Statement: [Wade Kinsella, hasLoveLifeCharacteristic, complicated love life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoveLifeCharacteristic Context triple: [Wade Kinsella, hasLoveLifeCharacteristic, complicated love life]
-
A.
hasSexualityCharacteristic
Indicates that an entity possesses a specific sexual orientation or sexuality-related characteristic.
-
B.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
C.
hasRoleInLifeOf
Indicates that one entity plays a particular role or function in the life or personal experience of another entity.
-
D.
hasSex
Indicates that one entity engages in sexual activity with another entity.
-
E.
spouseOrLover
Indicates a romantic partnership between two entities, whether formalized as a spouse or existing as a lover.
- F. None of above. chosen
Provenance (4 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a4aad4819097384e1b591be2e3 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.