Triple
T7672229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heigh-Ho |
E173774
|
entity |
| Predicate | lyricLine |
P41008
|
FINISHED |
| Object | Heigh-ho, heigh-ho, it's off to work we go |
—
|
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: Heigh-ho, heigh-ho, it's off to work we go | Statement: [Heigh-Ho, lyricLine, Heigh-ho, heigh-ho, it's off to work we go]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricLine Context triple: [Heigh-Ho, lyricLine, Heigh-ho, heigh-ho, it's off to work we go]
-
A.
lyricalPhrase
chosen
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
-
B.
hasRhymeLine
Indicates that one line of text rhymes with another line.
-
C.
lyricType
Indicates the specific category or role that a lyric plays within a musical or lyrical work (e.g., verse, chorus, bridge).
-
D.
lyricSetting
Indicates that one entity serves as the text or lyrics that are set to music or otherwise musically realized by another entity.
-
E.
lyricReference
Indicates that one entity (typically a work or text) contains or makes a reference to the lyrics of 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.