Triple
T32667212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Kirkwood Jr. |
E835187
|
entity |
| Predicate | coWroteBookForMusical |
P85240
|
FINISHED |
| Object | A Chorus Line |
—
|
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: A Chorus Line | Statement: [James Kirkwood Jr., coWroteBookForMusical, A Chorus Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coWroteBookForMusical Context triple: [James Kirkwood Jr., coWroteBookForMusical, A Chorus Line]
-
A.
wroteBookForMusical
chosen
Indicates that an entity authored a book specifically for a musical production or adaptation.
-
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.
writtenForPerformer
Indicates that a work was specifically composed or created to be performed by a particular performer or type of performer.
-
E.
hasWrittenSongsFor
Indicates that one entity has composed songs specifically intended to be performed, recorded, or used by another 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7a9734c81909c42ab13b7b33001 |
completed | May 3, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:08 a.m.