Triple
T36851197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantasmagoria |
E910679
|
entity |
| Predicate | approximateBudget |
P4259
|
FINISHED |
| Object | high for its time |
—
|
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 for its time | Statement: [Phantasmagoria, approximateBudget, high for its time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateBudget Context triple: [Phantasmagoria, approximateBudget, high for its time]
-
A.
estimatedCost
chosen
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
B.
approximateEstimation
Indicates an estimation relationship where one value or assessment is only roughly or closely, but not exactly, equal to another.
-
C.
budgetFrom
Indicates that a budget or funding allocation originates from or is provided by a particular source.
-
D.
rangeCityApprox
Indicates that an entity is located within an approximate geographic range of a specified city, rather than at an exact or strictly defined boundary.
-
E.
reportedBudget
Indicates that a specific budget amount or plan has been formally stated or disclosed, typically by one party to another or to the public.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:13 p.m.