Triple
T36977454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberal Food Plan |
E914738
|
entity |
| Predicate | relativeCostLevel |
P9543
|
FINISHED |
| Object | higher than Thrifty Food Plan |
—
|
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: higher than Thrifty Food Plan | Statement: [Liberal Food Plan, relativeCostLevel, higher than Thrifty Food Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeCostLevel Context triple: [Liberal Food Plan, relativeCostLevel, higher than Thrifty Food Plan]
-
A.
relativeLevel
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of another entity.
-
B.
listingCostLevel
Indicates the relative price range or expense level associated with a particular listing.
-
C.
reducedCostOf
Indicates that one entity represents a lowered or discounted cost associated with another entity, typically compared to a standard or original price.
-
D.
relativePrice
chosen
Indicates a comparison of the cost or monetary value of one entity relative to another.
-
E.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.