Triple
T33530525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sue |
E858765
|
entity |
| Predicate | hasFetishFor |
P183145
|
FINISHED |
| Object | Santa Claus |
—
|
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: Santa Claus | Statement: [Sue, hasFetishFor, Santa Claus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFetishFor Context triple: [Sue, hasFetishFor, Santa Claus]
-
A.
hasFetish
chosen
Indicates a relationship where one entity has a strong sexual fixation, attraction, or arousal specifically focused on another entity or on a particular object, body part, or activity.
-
B.
hasSexualityCharacteristic
Indicates that an entity possesses a specific sexual orientation or sexuality-related characteristic.
-
C.
coneSex
Indicates a sexual or mating relationship involving a cone-shaped structure or entity.
-
D.
hasRepressedDesireFor
Indicates that one entity harbors a hidden or unacknowledged longing or attraction toward another entity.
-
E.
rumoredLoverOf
Indicates that one entity is widely believed or speculated to be the romantic partner or lover of another entity, without confirmed evidence.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 1, 2026, 1:39 a.m.