Triple
T18504422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Let’s Talk About Sex |
E452162
|
entity |
| Predicate | isMajorHit |
P131919
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Let’s Talk About Sex, isMajorHit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorHit Context triple: [Let’s Talk About Sex, isMajorHit, true]
-
A.
isMajorHitIn
Indicates that a work (such as a song, film, or product) achieved major commercial success or popularity within a specified market, region, or context.
-
B.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
C.
isMajorSeeWithin
Indicates that one entity is the primary or most significant location or area encompassed within the boundaries of another entity.
-
D.
isMajorHighlightOf
Indicates that something serves as a primary or especially notable feature, event, or focal point within a larger context or whole.
-
E.
hasMajor
Indicates that an entity (typically a person or student) has a specific primary field of academic study or specialization.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53341063c81908361b0eb78794145 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:36 a.m.