Triple
T31315310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor Swift re-recordings |
E798577
|
entity |
| Predicate | hasFanResponse |
P18289
|
FINISHED |
| Object | strong fan support for Taylor’s Version releases |
—
|
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: strong fan support for Taylor’s Version releases | Statement: [Taylor Swift re-recordings, hasFanResponse, strong fan support for Taylor’s Version releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanResponse Context triple: [Taylor Swift re-recordings, hasFanResponse, strong fan support for Taylor’s Version releases]
-
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.
hasFanStatus
Indicates that one entity holds the role or condition of being a fan of another entity.
-
D.
isFanGiven
Indicates that one entity has been provided or supplied with a fan by another entity.
-
E.
hasFanUse
Indicates that something is used or operated by a fan (a person who admires or supports it).
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 29, 2026, 9:15 p.m.