Triple
T27773171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Inches" locker room speech |
E701810
|
entity |
| Predicate | audienceWithinFilm |
P99109
|
FINISHED |
| Object | Miami Sharks players |
—
|
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: Miami Sharks players | Statement: ["Inches" locker room speech, audienceWithinFilm, Miami Sharks players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceWithinFilm Context triple: ["Inches" locker room speech, audienceWithinFilm, Miami Sharks players]
-
A.
audienceWithinPlay
Indicates that the audience is located within the spatial or conceptual bounds of the play.
-
B.
targetAudienceOfFilms
Indicates the group of people or demographic segment that a particular film is primarily intended or designed to appeal to.
-
C.
audienceWithinStory
chosen
Indicates that an audience exists as an internal, in-story observer or listener within the narrative itself, rather than outside it.
-
D.
premiereAudienceType
Indicates the type or category of audience for whom a premiere event is intended or designated.
-
E.
filmedBeforeAudience
Indicates that the filming of an event, performance, or production took place in front of a live audience.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63797ab708190876c93bc93b05043 |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:36 p.m.