Triple
T16032744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austin mining district |
E388886
|
entity |
| Predicate | commodityByproduct |
P65738
|
FINISHED |
| Object | lead |
—
|
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: lead | Statement: [Austin mining district, commodityByproduct, lead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commodityByproduct Context triple: [Austin mining district, commodityByproduct, lead]
-
A.
commodityProduced
Indicates that a particular commodity is generated, manufactured, or otherwise produced by a specified entity or process.
-
B.
commodity
Indicates that one entity is a tradable good or resource that is bought, sold, or exchanged in relation to another entity.
-
C.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
-
D.
commodityClass
Indicates that one entity is classified as belonging to a particular category or class of commodities in relation to another entity.
-
E.
secondaryProducts
chosen
Indicates that certain entities arise as secondary or byproduct outputs from a primary process, activity, or production.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.