Triple
T33828938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rab |
E867040
|
entity |
| Predicate | hasTitleCharacterInContext |
P194378
|
FINISHED |
| Object | Sunshine on Leith (stage musical) |
—
|
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: Sunshine on Leith (stage musical) | Statement: [Rab, hasTitleCharacterInContext, Sunshine on Leith (stage musical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCharacterInContext Context triple: [Rab, hasTitleCharacterInContext, Sunshine on Leith (stage musical)]
-
A.
hasTitleCharacterFrom
Indicates that a work has a title that includes or is derived from a specific character.
-
B.
hasTitleCharacterAction
Indicates that a work’s title explicitly references or is derived from an action performed by a character within that work.
-
C.
hasTitleCharacterLocation
Indicates that a title or heading is associated with a specific character’s location within a text or media.
-
D.
isTitleCharacterString
Indicates that a given string represents the title text associated with an entity.
-
E.
hasTitleLetter
Indicates that an entity possesses a specific letter or character within its title.
- F. None of above. chosen
Provenance (4 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 1, 2026, 1:46 a.m.