Triple
T38228658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Away in a Manger |
E1012222
|
entity |
| Predicate | lyricsAttributionStatus |
P127756
|
FINISHED |
| Object | spurious |
—
|
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: spurious | Statement: [Away in a Manger, lyricsAttributionStatus, spurious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricsAttributionStatus Context triple: [Away in a Manger, lyricsAttributionStatus, spurious]
-
A.
lyricsAttributedTo
Indicates that the authorship or creation of a set of lyrics is credited to a particular person or entity.
-
B.
lyricStatus
chosen
Indicates the relationship between a musical work and the current state or condition of its lyrics (e.g., whether they are present, complete, verified, or otherwise annotated).
-
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.
lyricsBy
Indicates that the lyrics of a song or musical work were written or authored by a specified person or entity.
-
E.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.