Triple
T34005282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ella y Yo |
E871941
|
entity |
| Predicate | isStorySong |
P56230
|
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: [Ella y Yo, isStorySong, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStorySong Context triple: [Ella y Yo, isStorySong, true]
-
A.
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.
-
B.
isSongIn
Indicates that a particular song is contained within or belongs to a specified collection, such as an album, playlist, or soundtrack.
-
C.
isBalladAbout
Indicates that a ballad’s subject matter or narrative content centers on, references, or is dedicated to a particular entity or theme.
-
D.
hasFictionalSong
chosen
Indicates that one entity includes, features, or is associated with a song that is fictional or exists only within a narrative context.
-
E.
isForSong
Indicates that something is intended to be used with, associated with, or applicable to a particular song.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.