Triple
T33942085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petite Fleur |
E870190
|
entity |
| Predicate | hasLaterVersionsWithLyrics |
P63839
|
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: [Petite Fleur, hasLaterVersionsWithLyrics, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterVersionsWithLyrics Context triple: [Petite Fleur, hasLaterVersionsWithLyrics, true]
-
A.
hasLyricalVariant
chosen
Indicates that one item has an alternative version that differs in its lyrics while remaining related to the original.
-
B.
hasAdditionalLyrics
Indicates that an entity (such as a song or track) includes extra or supplementary lyrics beyond a primary or original set.
-
C.
hasAdditionalLyricsBy
Indicates that an entity (such as a musical work or track) includes extra or modified lyrics contributed by a specified person or group beyond the original lyricist.
-
D.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
E.
laterHadLyricsIn
Indicates that lyrics were added to a previously existing work at a later time.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 1, 2026, 1:49 a.m.