Triple
T34428170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikey and Nicky |
E883746
|
entity |
| Predicate | screenDebutInDirectionFor |
P45223
|
FINISHED |
| Object | Elaine May |
—
|
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: Elaine May | Statement: [Mikey and Nicky, screenDebutInDirectionFor, Elaine May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenDebutInDirectionFor Context triple: [Mikey and Nicky, screenDebutInDirectionFor, Elaine May]
-
A.
screenDebut
Indicates the event or relationship in which an entity appears on screen for the first time in a film, television, or other visual media production.
-
B.
screenDebutTypeFor
Indicates the type or category of screen debut associated with a given entity (e.g., a person or work).
-
C.
directionOfAppearance
Indicates the spatial direction or orientation from which something becomes visible or appears relative to a reference point or observer.
-
D.
screenDebutInFeatureFilmDirectionFor
chosen
Indicates that an entity made their first appearance as a director in a feature film for the specified work.
-
E.
scanDirection
Indicates the direction or orientation in which a scanning action is performed or data is acquired.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 2 a.m.