Triple
T18920951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Straw |
E462852
|
entity |
| Predicate | producedFromPart |
P11047
|
FINISHED |
| Object | Stems of cereal crops |
—
|
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: Stems of cereal crops | Statement: [Straw, producedFromPart, Stems of cereal crops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedFromPart Context triple: [Straw, producedFromPart, Stems of cereal crops]
-
A.
partOfProduction
Indicates that one entity functions as a component, segment, or phase within the overall process or structure of another production.
-
B.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
C.
builtAsPartOf
Indicates that one entity was constructed as a component or subset of a larger, encompassing entity or project.
-
D.
componentTypeProduced
Indicates that one entity produces or manufactures a specific type of component as an output of its activity or process.
-
E.
builtFrom
chosen
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9b3b93c819085032d8251a43ca8 |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.