Triple
T15310335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primient |
E366017
|
entity |
| Predicate | sourceOfRawMaterials |
P53073
|
FINISHED |
| Object | agricultural commodities |
—
|
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: agricultural commodities | Statement: [Primient, sourceOfRawMaterials, agricultural commodities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceOfRawMaterials Context triple: [Primient, sourceOfRawMaterials, agricultural commodities]
-
A.
materialSource
chosen
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
B.
hasSourceMaterial
Indicates that something is derived from, based on, or created using a particular source material.
-
C.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
-
D.
materialFromQuarriesUsedFor
Indicates that material extracted from quarries is used for a particular purpose, project, or object.
-
E.
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.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03cd176708190b0f6ba17aed92f8e |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.