Triple
T20221937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bisbee, Arizona |
E495276
|
entity |
| Predicate | wasMajorProducerOf |
P33520
|
FINISHED |
| Object | copper |
—
|
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: copper | Statement: [Bisbee, Arizona, wasMajorProducerOf, copper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorProducerOf Context triple: [Bisbee, Arizona, wasMajorProducerOf, copper]
-
A.
isMajorProducerOf
chosen
Indicates that an entity plays a leading or highly significant role in producing or supplying a particular product, resource, or output.
-
B.
workedAsProducerFor
Indicates that one entity served in the role of producer for a work, project, or production associated with another entity.
-
C.
notableProducer
Indicates that an entity is a significant or well-known producer associated with another entity, such as a work, product, or project.
-
D.
producedSaint
Indicates that an entity (such as a place, group, or lineage) has given rise to or brought forth a particular saint.
-
E.
producedNotableFiguresIn
Indicates that one entity (such as a place or institution) has given rise to or been the origin of notable or distinguished individuals associated with it.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd610f881908fdd22b1f8bd2efc |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.