Triple
T23321274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rage Against the Machine for Christmas No.1 (2009) |
E591155
|
entity |
| Predicate | wasFanLed |
P18289
|
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: [Rage Against the Machine for Christmas No.1 (2009), wasFanLed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFanLed Context triple: [Rage Against the Machine for Christmas No.1 (2009), wasFanLed, true]
-
A.
hasFan
Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
-
B.
hasFanActivity
chosen
Indicates that an entity is associated with actions, behaviors, or engagement carried out by fans in relation to it.
-
C.
isFanGiven
Indicates that one entity has been provided or supplied with a fan by another entity.
-
D.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
E.
hasFanTributeUse
Indicates that something is used, referenced, or incorporated within a fan-created tribute to a work, person, or entity.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19785ae5481908816b37da95ceb3e |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:07 p.m.