Triple
T21446385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferris Bueller |
E529086
|
entity |
| Predicate | hasOnScreenNarration |
P46114
|
FINISHED |
| Object | direct address to 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: direct address to audience | Statement: [Ferris Bueller, hasOnScreenNarration, direct address to audience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnScreenNarration Context triple: [Ferris Bueller, hasOnScreenNarration, direct address to audience]
-
A.
hasNarration
chosen
Indicates that an entity provides spoken or written commentary or storytelling for another entity, such as a work, event, or scene.
-
B.
hasCoNarrator
Indicates that two or more entities share the role of narrating the same work, event, or story together.
-
C.
narratedTo
Indicates that one entity tells or recounts a story, event, or information directly to another entity as the audience.
-
D.
narrationRequired
Indicates that an accompanying explanatory or descriptive narrative is required to properly present or understand the related content or event.
-
E.
hasOnscreenFunction
Indicates that an entity serves a particular role or performs a specific function when it appears on screen.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9cea7bc81909ee3e1cdeda1fe7e |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:06 p.m.