Triple
T21450133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | They're Playing Our Song (stage musical, story basis) |
E529185
|
entity |
| Predicate | hasRoleOf |
P161
|
FINISHED |
| Object | lyricist |
—
|
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: lyricist | Statement: [They're Playing Our Song (stage musical, story basis), hasRoleOf, lyricist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleOf Context triple: [They're Playing Our Song (stage musical, story basis), hasRoleOf, lyricist]
-
A.
hasRole
chosen
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
-
C.
mayHaveRole
Indicates that an entity is permitted or eligible to hold or perform a specified role.
-
D.
hasRoleCharacteristic
Indicates that an entity possesses a specific characteristic, quality, or attribute associated with a particular role.
-
E.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d281c0819080c3f8a58947a115 |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:06 p.m.