Triple
T24331746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beast from Haunted Cave |
E613261
|
entity |
| Predicate | budgetCharacteristic |
P155744
|
FINISHED |
| Object | low-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: low-budget | Statement: [Beast from Haunted Cave, budgetCharacteristic, low-budget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetCharacteristic Context triple: [Beast from Haunted Cave, budgetCharacteristic, low-budget]
-
A.
budgetType
Indicates the classification or category of a budget associated with an entity or financial activity.
-
B.
budgetAccount
Indicates a relationship where an entity is associated with, charged to, or managed under a specific budget account for financial tracking or allocation.
-
C.
budgetItemOf
Indicates that one entity is a specific budget line or allocation that belongs to, or is part of, another entity’s overall budget.
-
D.
budgetUnit
Indicates that one entity functions as the budgetary unit or cost-accounting unit associated with another entity within a financial or organizational context.
-
E.
budget
Indicates that an entity allocates, plans, or assigns specific financial resources for another entity, activity, or time period.
- F. None of above. chosen
Provenance (4 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292f1312081909d44baa1e296c735 |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28b7ff1808190870dfe9af789a1eb |
completed | April 29, 2026, 10:51 p.m. |
Created at: April 18, 2026, 1:55 a.m.