Triple
T21145896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochaline silica sand mine |
E521053
|
entity |
| Predicate | usedForProduct |
P143049
|
FINISHED |
| Object | container glass |
—
|
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: container glass | Statement: [Lochaline silica sand mine, usedForProduct, container glass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForProduct Context triple: [Lochaline silica sand mine, usedForProduct, container glass]
-
A.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
usesProductFrom
Indicates that one entity makes use of or employs a product that originates from or is provided by another entity.
-
C.
usesProduct
Indicates that one entity makes use of, applies, or employs a particular product.
-
D.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
E.
usedInECommerce
Indicates that something is employed or applied within the context of electronic commerce activities or systems.
- F. None of above. chosen
Provenance (4 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723fdc25481909d6648e09b069c41 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:58 p.m.