Triple
T23170475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'm a Fool to Want You |
E578842
|
entity |
| Predicate | isWidelyCoveredIn |
P151206
|
FINISHED |
| Object | jazz |
—
|
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: jazz | Statement: [I'm a Fool to Want You, isWidelyCoveredIn, jazz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWidelyCoveredIn Context triple: [I'm a Fool to Want You, isWidelyCoveredIn, jazz]
-
A.
widelyCoveredBy
Indicates that something (such as an event, topic, or issue) receives extensive attention or reporting from many media outlets or information sources.
-
B.
isWidelyKnown
Indicates that something is generally recognized or familiar to a large number of people.
-
C.
isFrequentlyCovered
Indicates that an entity is regularly or commonly reported on, discussed, or featured, especially in media or informational sources.
-
D.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
E.
isFrequentlyCoveredSince
Indicates that one entity has been regularly or repeatedly covered (e.g., in media, reports, or discussions) starting from a specified point in time.
- 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2f10208190b3a0f9a4c790cb0a |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:03 p.m.