Triple
T19959759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidalia onion |
E479780
|
entity |
| Predicate | hasLowSulfurContent |
P13885
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Vidalia onion, hasLowSulfurContent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowSulfurContent Context triple: [Vidalia onion, hasLowSulfurContent, true]
-
A.
typicalSulfurLimit
Indicates the usual or standard upper bound on the amount of sulfur allowed or present in a given context.
-
B.
hasSulfurOdor
Indicates that an entity emits or possesses an odor characteristic of sulfur or sulfur-containing compounds.
-
C.
hasLow
chosen
Indicates that an entity possesses a value, level, or amount of something that is below a defined or expected threshold.
-
D.
isGasRich
Indicates that an entity possesses a relatively high abundance or concentration of gas compared to a defined reference or threshold.
-
E.
hasTypicalCarbonContentRange
Indicates the usual lower and upper bounds of carbon content typically found in or associated with an entity.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af386548190aefac1e40aac403d |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.