Triple
T38392731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Songs for a New World |
E899768
|
entity |
| Predicate | originalCastIncludes |
P60536
|
FINISHED |
| Object | Brooks Ashmanskas |
E1626937
|
NE 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: Brooks Ashmanskas | Statement: [Songs for a New World, originalCastIncludes, Brooks Ashmanskas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCastIncludes Context triple: [Songs for a New World, originalCastIncludes, Brooks Ashmanskas]
-
A.
mainCastIncludes
Indicates that a work’s primary cast features the specified person or character as one of its main members.
-
B.
originalCast
Indicates that the subject is a member of the initial group of performers or participants who first originated a role or production.
-
C.
originalCastPerformer
chosen
Indicates that a performer was part of the original cast in the first production or release of a work.
-
D.
includesCastMembersFrom
Indicates that one entity’s cast list contains one or more cast members who also appear in the cast list of another entity.
-
E.
hasHumanCast
Indicates that a work or production features human performers as part of its cast.
- F. None of above.
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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41b2b0e530819086de2b48752bf4d9 |
completed | June 28, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.