Triple
T25008191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Cape |
E625907
|
entity |
| Predicate | hasNotableLyricMotif |
P4921
|
FINISHED |
| Object | flying away |
—
|
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: flying away | Statement: [Red Cape, hasNotableLyricMotif, flying away]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLyricMotif Context triple: [Red Cape, hasNotableLyricMotif, flying away]
-
A.
hasLyricsMentioning
Indicates that the referenced lyrics explicitly mention or refer to the specified entity.
-
B.
hasLyricalTheme
chosen
Indicates that one entity (typically a creative work) features or is characterized by a particular lyrical subject, topic, or theme.
-
C.
notableSongCharacteristic
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
D.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
E.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 18, 2026, 6:05 a.m.