Triple
T30020562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawrence D. Cohen |
E762723
|
entity |
| Predicate | co-wroteBookFor |
P47055
|
FINISHED |
| Object | Carrie (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: Carrie (musical) | Statement: [Lawrence D. Cohen, co-wroteBookFor, Carrie (musical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: co-wroteBookFor Context triple: [Lawrence D. Cohen, co-wroteBookFor, Carrie (musical)]
-
A.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
B.
workWrittenFor
Indicates that a creative work was specifically composed, produced, or created for a particular person, group, event, purpose, or medium.
-
C.
coAuthorOfLibrettoWith
Indicates that two or more individuals collaborated in writing the same libretto.
-
D.
workOfAuthorOf
Indicates that one entity is a work (such as a book, article, or artwork) created by the author associated with another entity.
-
E.
hasWritingCreditOn
chosen
Indicates that an entity is credited as a writer or co-writer for a particular work or production.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67987d8548190ad2276a4bc4c7a10 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:47 p.m.