Triple
T23272952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lefty Dizz |
E588337
|
entity |
| Predicate | stageBehavior |
P91006
|
FINISHED |
| Object | frequent interaction with audience |
—
|
LITERAL 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: frequent interaction with audience | Statement: [Lefty Dizz, stageBehavior, frequent interaction with audience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageBehavior Context triple: [Lefty Dizz, stageBehavior, frequent interaction with audience]
-
A.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
-
B.
coreStageBehavior
chosen
Indicates the fundamental or default way an entity acts or responds in a given context or process.
-
C.
stageFunction
Indicates that an entity organizes, hosts, or presents a performance, event, or function.
-
D.
stageContext
Indicates the situational or environmental setting in which an event, action, or interaction takes place.
-
E.
stageName
Indicates that one entity is the performance or professional name 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957518f88190bdd88ccc4e295668 |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:47 p.m.