Triple
T25384223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get Right Intae Him! |
E631477
|
entity |
| Predicate | spokenWordArtist |
P141257
|
FINISHED |
| Object | Billy Connolly |
—
|
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: Billy Connolly | Statement: [Get Right Intae Him!, spokenWordArtist, Billy Connolly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenWordArtist Context triple: [Get Right Intae Him!, spokenWordArtist, Billy Connolly]
-
A.
notableSpokenWordPerformer
Indicates that the subject is a well-known or distinguished performer in spoken word, such as poetry, storytelling, or similar verbal performance arts.
-
B.
artistOf
chosen
Indicates that one entity is the creator or performer responsible for producing a particular work or piece.
-
C.
spokenWord
Indicates that one entity has uttered or articulated a specific word or phrase in spoken form.
-
D.
publishedArtist
Indicates that one entity has published, released, or made public the creative work or content produced by the artist entity.
-
E.
producerArtist
Indicates that one entity serves as the producer (e.g., overseeing or managing the creation) of a work created or performed by the artist 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f56566c5408190a8841d2c45dcf52c |
completed | May 2, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:46 p.m.