Triple
T21678642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mockingbird |
E535040
|
entity |
| Predicate | hasLyricOrigin |
P4872
|
FINISHED |
| Object | traditional lullaby lyrics adapted |
—
|
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: traditional lullaby lyrics adapted | Statement: [Mockingbird, hasLyricOrigin, traditional lullaby lyrics adapted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLyricOrigin Context triple: [Mockingbird, hasLyricOrigin, traditional lullaby lyrics adapted]
-
A.
hasOriginalLyricist
Indicates that an entity (such as a musical or song) is associated with the person who first wrote its lyrics.
-
B.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
C.
hasLyricsSource
chosen
Indicates that one entity serves as the source or origin of the lyrics associated with another entity.
-
D.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
E.
hasLyricsFeature
Indicates that something possesses a particular characteristic or attribute related to its lyrics.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a11088081908911af2629f54c1c |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:43 p.m.