Triple
T13695156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jay (The 40-Year-Old Virgin) |
E328364
|
entity |
| Predicate | adviceStyle |
P111205
|
FINISHED |
| Object | crude |
—
|
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: crude | Statement: [Jay (The 40-Year-Old Virgin), adviceStyle, crude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adviceStyle Context triple: [Jay (The 40-Year-Old Virgin), adviceStyle, crude]
-
A.
providesAdviceOn
Indicates that one entity gives guidance, recommendations, or expert counsel to another entity regarding a particular subject or matter.
-
B.
adaptationStyle
Indicates how an entity adjusts or modifies its behavior, form, or strategy in response to changing conditions or influences.
-
C.
advises
Indicates that one entity provides guidance, recommendations, or counsel to another entity.
-
D.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
-
E.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8773f388190b2413b1e05fd5fd7 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.