Triple
T13461280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grube Samson |
E311371
|
entity |
| Predicate | alsoMined |
P73907
|
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: [Grube Samson, alsoMined, lead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoMined Context triple: [Grube Samson, alsoMined, lead]
-
A.
minedSince
Indicates that a resource or material has been extracted from a location continuously starting from a specified point in time.
-
B.
associatedMine
chosen
Indicates that one entity is linked or connected to a particular mine, typically as its source, location, or relevant mining site.
-
C.
notableMiner
Indicates that an entity is recognized as a miner of particular significance or prominence.
-
D.
minedBy
Indicates that a resource, material, or location is extracted or obtained through mining activities performed by a specified agent or entity.
-
E.
miningHistory
Indicates a historical record or past occurrence of mining-related activities or operations associated with an 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0d95fc81909d9f73d5315dc7b4 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03dcd0c8190a8927eb4eaad1c45 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.