Triple
T21490334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Jon |
E530218
|
entity |
| Predicate | protagonistHabit |
P41014
|
FINISHED |
| Object | frequent pornography consumption |
—
|
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: frequent pornography consumption | Statement: [Don Jon, protagonistHabit, frequent pornography consumption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistHabit Context triple: [Don Jon, protagonistHabit, frequent pornography consumption]
-
A.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
B.
habitNumber
Indicates a numerical designation or identifier assigned to a particular habit within a set or sequence of habits.
-
C.
protagonistAction
Indicates that the referenced entity performs the central or primary action associated with the main character in a narrative or scenario.
-
D.
hasHabit
chosen
Indicates that an entity regularly performs, practices, or exhibits a particular behavior or routine.
-
E.
associatedCharacterTrait
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea3aee648190ba845f0c7d8110dd |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.