Triple
T37565482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobalt, Ontario |
E933943
|
entity |
| Predicate | discoveryOfResource |
P75389
|
FINISHED |
| Object | rich silver deposits in early 1900s |
—
|
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: rich silver deposits in early 1900s | Statement: [Cobalt, Ontario, discoveryOfResource, rich silver deposits in early 1900s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryOfResource Context triple: [Cobalt, Ontario, discoveryOfResource, rich silver deposits in early 1900s]
-
A.
discoveredResource
chosen
Indicates that an entity has found, identified, or uncovered a particular resource.
-
B.
coveredResource
Indicates that one entity serves as a resource that is included within the scope or protection of another entity (such as a policy, agreement, or coverage).
-
C.
discoveredFeature
Indicates that an entity has identified or uncovered a previously unknown or unrecognized feature of another entity or object.
-
D.
discoveryEvent
Indicates an event in which something previously unknown or unrecognized is found, identified, or revealed.
-
E.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.