Triple
T31418253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenny |
E801456
|
entity |
| Predicate | associatedWithTheatreScene |
P74548
|
FINISHED |
| Object | Off-Broadway |
E85030
|
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: Off-Broadway | Statement: [Lenny, associatedWithTheatreScene, Off-Broadway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTheatreScene Context triple: [Lenny, associatedWithTheatreScene, Off-Broadway]
-
A.
partOfTheatre
Indicates that one entity is a component, section, or subdivision of a theatre.
-
B.
belongsToTheatre
Indicates that something is a member, part, or property of a particular theatre or theatre organization.
-
C.
relatedToTheatre
chosen
Indicates a general association or connection with theatre, such as involvement, relevance, or contextual relation to theatrical arts or activities.
-
D.
theatreOf
Indicates that an event, action, or operation takes place within or is primarily associated with a particular theatre or venue.
-
E.
sceneAssociation
Indicates a contextual or thematic relationship linking entities that co-occur or interact within the same scene.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b07709f988190ab00938539763f34 |
completed | June 11, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 8:45 p.m.