Triple
T18646081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinball Wizard |
E455806
|
entity |
| Predicate | coveredFor |
P13946
|
FINISHED |
| Object | film adaptation of Tommy |
—
|
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: film adaptation of Tommy | Statement: [Pinball Wizard, coveredFor, film adaptation of Tommy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredFor Context triple: [Pinball Wizard, coveredFor, film adaptation of Tommy]
-
A.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
B.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
C.
coverUpBy
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing associated with another entity.
-
D.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
E.
alsoCovers
chosen
Indicates that something extends its scope or applicability to include an additional subject, area, or case beyond what was originally covered.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500d69648190800da65de0c191b8 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.