Triple
T38678970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Martin |
E943834
|
entity |
| Predicate | originalStarOf |
P60536
|
FINISHED |
| Object | The Drowsy Chaperone |
E279678
|
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: The Drowsy Chaperone | Statement: [Bob Martin, originalStarOf, The Drowsy Chaperone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalStarOf Context triple: [Bob Martin, originalStarOf, The Drowsy Chaperone]
-
A.
starredActor
Indicates that an actor performed a leading or significant role in a particular production or work.
-
B.
starredActorWith
Indicates that one entity participated as an actor in a production together with another specified actor.
-
C.
isPrimaryStarOf
Indicates that a star serves as the main or central stellar object in relation to a specified system, object, or context.
-
D.
originalCastPerformer
chosen
Indicates that a performer was part of the original cast in the first production or release of a work.
-
E.
notableStar
Indicates that the subject is a star (or stellar object) that is distinguished or noteworthy in some significant way, such as brightness, fame, or scientific interest, relative to other stars.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4223a94c988190b08b7fee382e3d00 |
completed | June 29, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.