Triple
T14528363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lost in the Woods |
E340836
|
entity |
| Predicate | featuresEnsembleVocalsBy |
P88799
|
FINISHED |
| Object | reindeer chorus |
—
|
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: reindeer chorus | Statement: [Lost in the Woods, featuresEnsembleVocalsBy, reindeer chorus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresEnsembleVocalsBy Context triple: [Lost in the Woods, featuresEnsembleVocalsBy, reindeer chorus]
-
A.
featuresVocalEnsemble
chosen
Indicates that something includes or presents a group of vocal performers singing together.
-
B.
featuresVocalist
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
C.
featuresVocalCollaborations
Indicates that the work includes vocal performances by multiple distinct artists collaborating together.
-
D.
featuresSongwriter
Indicates that a musical work includes or credits a particular person as its songwriter.
-
E.
vocalForces
Indicates a relationship where one entity uses vocal expression (such as speech, singing, or sound) to exert influence, pressure, or compulsion on 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea051bc608190ad4d516c5e7bca43 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.