Triple
T24985669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Just Wright |
E625299
|
entity |
| Predicate | leadStudioPartner |
P48184
|
FINISHED |
| Object | Fox Searchlight Pictures |
—
|
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: Fox Searchlight Pictures | Statement: [Just Wright, leadStudioPartner, Fox Searchlight Pictures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadStudioPartner Context triple: [Just Wright, leadStudioPartner, Fox Searchlight Pictures]
-
A.
leadStudioStar
Indicates that a person is the primary or top-billed star in a studio’s production.
-
B.
partnerStudio
chosen
Indicates that one entity serves as a partner studio associated with, collaborating with, or officially linked to another entity.
-
C.
leadStudioHead
Indicates that one entity serves as the primary or head studio leader responsible for another entity (such as a project, production, or organization).
-
D.
launchPartner
Indicates that one entity collaborates closely with another as a primary partner during the initial launch or rollout of a product, service, or initiative.
-
E.
leadCallAndResponsePartner
Indicates a relationship where one entity initiates a call-and-response interaction and the other serves as its primary responding partner.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490a4a508190bdd6c2dde03e251a |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:03 a.m.