Triple
T29002802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeff Gutt |
E736348
|
entity |
| Predicate | performedCoverOnXFactor |
P124213
|
FINISHED |
| Object | “Hallelujah” |
—
|
NE NERFINISHED |
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: “Hallelujah” | Statement: [Jeff Gutt, performedCoverOnXFactor, “Hallelujah”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedCoverOnXFactor Context triple: [Jeff Gutt, performedCoverOnXFactor, “Hallelujah”]
-
A.
performedSongFor
Indicates that one entity performed a song specifically for another entity as the intended audience or recipient.
-
B.
coverPerformer
chosen
Indicates that one entity performs a cover version of a work originally created or performed by another entity.
-
C.
performedSong
Indicates that an entity (such as an artist or performer) has given a performance of a particular song.
-
D.
performsSongWith
Indicates that two or more entities jointly perform or present a song together.
-
E.
providedVocalPerformanceFor
Indicates that one entity delivered or contributed a vocal performance in support of, or as part of, another entity’s work, event, or production.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 28, 2026, 9:36 a.m.