Triple

T35646954
Position Surface form Disambiguated ID Type / Status
Subject The Puffy Chair E1030035 entity
Predicate hasBudgetCharacteristic 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: [The Puffy Chair, hasBudgetCharacteristic, low-budget]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBudgetCharacteristic
Context triple: [The Puffy Chair, hasBudgetCharacteristic, low-budget]
  • A. hasBudgetFor
    Indicates that an entity possesses sufficient allocated financial resources to support, fund, or carry out another specified entity, activity, or purpose.
  • B. budgetCharacteristic chosen
    Indicates that something has a particular budget-related property, such as a cost level, spending pattern, or financial constraint.
  • C. hasCapitalBudgetFor
    Indicates that an entity allocates or designates financial resources specifically for capital expenditures related to another entity or purpose.
  • D. hasPlanningCharacteristic
    Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
  • E. hasBusinessModelCharacteristic
    Indicates that a business model possesses or exhibits a specific feature, quality, or attribute.
  • 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_69f76e0938088190a8f199631e97dec3 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fce7671f108190bf3ebf54339068b5 completed May 7, 2026, 7:26 p.m.
PD Predicate disambiguation batch_69fce5b5a84c81908ac1b5b9f08d48d0 completed May 7, 2026, 7:19 p.m.
Created at: May 3, 2026, 4:05 p.m.