Triple
T17891155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broccoli |
E447318
|
entity |
| Predicate | isLowIn |
P13885
|
FINISHED |
| Object | Calories |
—
|
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: Calories | Statement: [Broccoli, isLowIn, Calories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLowIn Context triple: [Broccoli, isLowIn, Calories]
-
A.
hasLow
chosen
Indicates that an entity possesses a value, level, or amount of something that is below a defined or expected threshold.
-
B.
hasLowForm
Indicates that an entity possesses a lower or less developed form, version, or level of something relative to a standard or comparison.
-
C.
isLowland
Indicates that an entity is located in, associated with, or characteristic of lowland areas or low-lying terrain relative to surrounding regions.
-
D.
lowerValueIndicates
Indicates that a smaller numerical value of a property or measurement corresponds to a greater degree, better outcome, or stronger presence of the relevant characteristic.
-
E.
isLowUsageStation
Indicates that a station has relatively low levels of usage or activity compared to other stations.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7948888190b59ddc7061d13e84 |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.