Triple
T36977426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moderate-Cost Food Plan |
E914737
|
entity |
| Predicate | hasCostLevelLowerThan |
P32836
|
FINISHED |
| Object | Liberal 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: Liberal Food Plan | Statement: [Moderate-Cost Food Plan, hasCostLevelLowerThan, Liberal Food Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCostLevelLowerThan Context triple: [Moderate-Cost Food Plan, hasCostLevelLowerThan, Liberal Food Plan]
-
A.
hasLowerCostPerBitThan
Indicates that the cost required to transmit or store each unit of data (bit) for one entity is lower than that for another entity.
-
B.
hasLowerTier
chosen
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
-
C.
hasLowerDensityThan
Indicates that one entity has a lower density (mass per unit volume) compared to another entity.
-
D.
hasLowerMaxPowerThan
Indicates that the maximum power capacity or output of one entity is less than that of another entity.
-
E.
hasLowerLevelUse
Indicates that one entity is used or applied at a more detailed, specific, or subordinate level within the context of another entity’s use.
- 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.