Triple
T34094150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victorias Milling Company |
E874376
|
entity |
| Predicate | mainRawMaterial |
P5629
|
FINISHED |
| Object | sugarcane |
—
|
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: sugarcane | Statement: [Victorias Milling Company, mainRawMaterial, sugarcane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRawMaterial Context triple: [Victorias Milling Company, mainRawMaterial, sugarcane]
-
A.
originalMaterialFor
Indicates that one entity serves as the source or basis material from which another entity is derived, adapted, or created.
-
B.
originalCoreMaterial
Indicates that something is made from or based on the initial, primary material used before any changes, replacements, or modifications.
-
C.
primaryFeedstock
chosen
Indicates that one entity serves as the main raw material or input used to produce, process, or operate another entity.
-
D.
materialSource
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
E.
materialFormedIn
Indicates that a material is created, produced, or formed within a specified process, environment, or context.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:52 a.m.