Triple
T33349533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austin Powers theme and interludes |
E853894
|
entity |
| Predicate | featuresBandType |
P168798
|
FINISHED |
| Object | faux-mod band |
—
|
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: faux-mod band | Statement: [Austin Powers theme and interludes, featuresBandType, faux-mod band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBandType Context triple: [Austin Powers theme and interludes, featuresBandType, faux-mod band]
-
A.
creditedBandType
chosen
Indicates that an entity is credited specifically as a band of a particular type or classification in a given context.
-
B.
featuresBandMembers
Indicates that something includes or presents specific band members as part of its content or composition.
-
C.
bandNameType
Indicates that a given name functions specifically as the name or title of a musical band.
-
D.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
-
E.
featuresFictionalBand
Indicates that something (such as a work or event) includes or presents a fictional band as part of its content or narrative.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01ac8b4ac881908aa52079c985ddac |
completed | May 11, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_6a01aa7fa7b48190b4911aa6bcabe7eb |
completed | May 11, 2026, 10:07 a.m. |
Created at: May 1, 2026, 1:34 a.m.