Triple
T28206188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PoP! |
E717028
|
entity |
| Predicate | hasFictionalHitSong |
P20452
|
FINISHED |
| Object | PoP! Goes My Heart |
—
|
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: PoP! Goes My Heart | Statement: [PoP!, hasFictionalHitSong, PoP! Goes My Heart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalHitSong Context triple: [PoP!, hasFictionalHitSong, PoP! Goes My Heart]
-
A.
hasFictionalSong
Indicates that one entity includes, features, or is associated with a song that is fictional or exists only within a narrative context.
-
B.
hasSongAbout
Indicates that one entity has created, features, or is associated with a song whose subject or theme is about another entity.
-
C.
isFictionalSong
Indicates that the referenced song exists only in fiction (e.g., within a story, film, game, or other fictional context) and not as a real-world musical work.
-
D.
hasSong
chosen
Indicates that one entity possesses, features, or includes a particular song.
-
E.
hasFictionalDiscography
Indicates that an entity is associated with a discography that exists only within a fictional or narrative context, rather than as real-world musical releases.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 27, 2026, 10:35 p.m.