Triple
T32555031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Get Down |
E832073
|
entity |
| Predicate | originallyPlannedBudget |
P184111
|
FINISHED |
| Object | high-budget production |
—
|
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: high-budget production | Statement: [The Get Down, originallyPlannedBudget, high-budget production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyPlannedBudget Context triple: [The Get Down, originallyPlannedBudget, high-budget production]
-
A.
reportedBudget
chosen
Indicates that a specific budget amount or plan has been formally stated or disclosed, typically by one party to another or to the public.
-
B.
originallyPlannedFor
Indicates that something was initially intended, designed, or scheduled to be used for or associated with a particular purpose, event, or entity, regardless of what ultimately occurred.
-
C.
budgetFrom
Indicates that a budget or funding allocation originates from or is provided by a particular source.
-
D.
originalPlan
Indicates that one entity is the initial or primary plan or intended course of action associated with another entity.
-
E.
plannedAgainst
Indicates that an entity has formulated or coordinated plans targeting another entity, typically with opposing or adversarial intent.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01b841f5508190832bba00cf795bad |
completed | May 11, 2026, 11:06 a.m. |
| PD | Predicate disambiguation | batch_6a01b59541fc8190a9b13a55327c4aa1 |
completed | May 11, 2026, 10:55 a.m. |
Created at: May 1, 2026, 1:03 a.m.