Triple
T19959779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidalia onion |
E479780
|
entity |
| Predicate | isStoredAs |
P91294
|
FINISHED |
| Object | fresh onion |
—
|
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: fresh onion | Statement: [Vidalia onion, isStoredAs, fresh onion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStoredAs Context triple: [Vidalia onion, isStoredAs, fresh onion]
-
A.
storageFormat
chosen
Indicates the specific way in which data or content is physically or logically organized, encoded, and stored.
-
B.
canBeStoredFor
Indicates that something is suitable or allowed to be kept in storage for a certain duration or under certain conditions.
-
C.
isMajorStorageFor
Indicates that one entity serves as the primary or main storage location or repository for another entity.
-
D.
canBeStoredOn
Indicates that one entity is capable of being placed, kept, or maintained on another entity as a storage location.
-
E.
storageProperty
Indicates a relationship where an entity has a specific storage-related characteristic, such as capacity, type, or configuration.
- 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.