Triple
T21145886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochaline silica sand mine |
E521053
|
entity |
| Predicate | primaryUseOfOutput |
P131315
|
FINISHED |
| Object | glassmaking |
—
|
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: glassmaking | Statement: [Lochaline silica sand mine, primaryUseOfOutput, glassmaking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseOfOutput Context triple: [Lochaline silica sand mine, primaryUseOfOutput, glassmaking]
-
A.
primaryUseOf
chosen
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
B.
primaryOutput
Indicates that the related entity is the main or principal result, product, or outcome produced by another entity or process.
-
C.
originalPrimaryUse
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
-
D.
isPrimarilyUsedAs
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
E.
formerPrimaryUse
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
- 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_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. |
Created at: April 16, 2026, 2:58 p.m.