Triple
T20877016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finding Neverland |
E514044
|
entity |
| Predicate | castMember |
P1668
|
FINISHED |
| Object | Joe Prospero |
—
|
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: Joe Prospero | Statement: [Finding Neverland, castMember, Joe Prospero]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Joe Prospero Context triple: [Finding Neverland, castMember, Joe Prospero]
-
A.
Joe Prospero
chosen
Joe Prospero is a British actor best known for his role as one of the Llewelyn Davies boys in the film "Finding Neverland."
-
B.
Prospero
Prospero was the birth name of Pope Benedict XIV, an 18th-century pope noted for his scholarship and efforts to reconcile church doctrine with Enlightenment thought.
-
C.
Prospero
Prospero is an Italian surname notably borne by figures such as Ada Prospero Gobetti, a prominent anti-fascist, writer, and intellectual.
-
D.
Prospero
Prospero is the powerful sorcerer and rightful Duke of Milan who orchestrates the events on a remote island in Shakespeare’s play "The Tempest."
-
E.
Prospero
Prospero is the internal codename that was reportedly used by Sony during the development of the PlayStation 5 console.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c6767ec0819080721e2e75bd0d66 |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 12:45 p.m.