Triple
T5119227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fox 2000 Pictures |
E115417
|
entity |
| Predicate | targetBudgetRange |
P8208
|
FINISHED |
| Object | mid-budget |
—
|
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: mid-budget | Statement: [Fox 2000 Pictures, targetBudgetRange, mid-budget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetBudgetRange Context triple: [Fox 2000 Pictures, targetBudgetRange, mid-budget]
-
A.
budgetFrom
Indicates that a budget or funding allocation originates from or is provided by a particular source.
-
B.
budgetRight
Indicates that an entity has the authority, responsibility, or entitlement to allocate, manage, or decide on the use of a specified budget or financial resources.
-
C.
budgetTarget
Indicates that a specific financial goal or spending limit has been set for a given entity, period, or activity.
-
D.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
E.
budgetLevel
chosen
Indicates the relative amount of financial resources allocated or available for something, typically categorized by level (e.g., low, medium, high).
- 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_69bd4442ade0819087b9461f892b206b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
Created at: March 20, 2026, 1:42 p.m.