Triple
T31945672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H 81 |
E815644
|
entity |
| Predicate | referredWorkNumberOfSongs |
P10577
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [H 81, referredWorkNumberOfSongs, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referredWorkNumberOfSongs Context triple: [H 81, referredWorkNumberOfSongs, 6]
-
A.
numberOfSongs
chosen
Indicates the quantity of songs associated with a given entity.
-
B.
sangForSongsAssociatedWith
Indicates that one entity performed singing on behalf of, or in service of, another entity specifically for songs that are associated with that second entity.
-
C.
referencedByArtist
Indicates that an artist has mentioned, cited, or otherwise referred to the target entity in their work or related materials.
-
D.
hasUnderlyingWorkSongwriters
Indicates that a work is associated with the songwriters who created the underlying musical composition on which it is based.
-
E.
sourceSongWork
Indicates that one song work serves as the original source or basis from which another song work is derived, adapted, or referenced.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 1, 2026, 12:06 a.m.