Triple
T34094172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victorias Milling Company |
E874376
|
entity |
| Predicate | usesByproduct |
P92763
|
FINISHED |
| Object | bagasse |
—
|
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: bagasse | Statement: [Victorias Milling Company, usesByproduct, bagasse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesByproduct Context triple: [Victorias Milling Company, usesByproduct, bagasse]
-
A.
usedForProduct
Indicates that one entity serves as a tool, component, or means specifically employed in the creation, operation, or delivery of another entity considered as a product.
-
B.
usesProductFrom
Indicates that one entity makes use of or employs a product that originates from or is provided by another entity.
-
C.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
D.
usesProductionResourcesOf
Indicates that one entity makes use of the production resources (such as facilities, equipment, or infrastructure) that belong to or are operated by another entity.
-
E.
usesProduct
chosen
Indicates that one entity makes use of, applies, or employs a particular product.
- 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_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:52 a.m.