Triple
T38264097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lighters |
E1021006
|
entity |
| Predicate | memberOfActOnRecording |
P119358
|
FINISHED |
| Object | Bad Meets Evil |
—
|
NE NERFINISHED |
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: Bad Meets Evil | Statement: [Lighters, memberOfActOnRecording, Bad Meets Evil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfActOnRecording Context triple: [Lighters, memberOfActOnRecording, Bad Meets Evil]
-
A.
roleInRecording
chosen
Indicates that an entity holds a specific role or function in the creation or performance of a particular recording.
-
B.
participantRecorded
Indicates that information about a participant has been captured and stored in some form of record or system.
-
C.
reRecordedWith
Indicates that an existing recording was made again in collaboration with the specified entity (such as an artist, group, or producer).
-
D.
usedForRecordingBy
Indicates that something serves as a medium, tool, or device that is employed by an agent to make a recording.
-
E.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
- 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.