Triple
T32699552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Red Red |
E836103
|
entity |
| Predicate | hasOriginalPerformance |
P29315
|
FINISHED |
| Object | Fiona Apple |
—
|
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: Fiona Apple | Statement: [Red Red Red, hasOriginalPerformance, Fiona Apple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalPerformance Context triple: [Red Red Red, hasOriginalPerformance, Fiona Apple]
-
A.
originalPerformanceFor
chosen
Indicates that one entity is the original performance or execution from which another related version, recording, or representation is derived.
-
B.
hasOriginalMusicBy
Indicates that the original musical score or soundtrack for a work was created or composed by a specified entity.
-
C.
hasOriginalScoreAlbum
Indicates that an entity is associated with a specific album containing its original musical score.
-
D.
hasOriginalSongReleaseContext
Indicates that an original song is associated with a specific context in which it was first released (such as an event, medium, or setting).
-
E.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 1, 2026, 1:10 a.m.