Triple
T26815286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schefferville |
E672107
|
entity |
| Predicate | oreDeposit |
P161498
|
FINISHED |
| Object | high-grade hematite |
—
|
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: high-grade hematite | Statement: [Schefferville, oreDeposit, high-grade hematite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oreDeposit Context triple: [Schefferville, oreDeposit, high-grade hematite]
-
A.
oreDepositType
Indicates the specific classification of an ore deposit based on how it formed or its characteristic geological features.
-
B.
depositary
Indicates that one entity holds or safeguards something (such as assets, documents, or funds) on behalf of another entity.
-
C.
deposited
Indicates that an entity has placed or put something into another entity, typically transferring it into a container, location, or account.
-
D.
depositType
Indicates the specific kind or category of deposit associated with an account, transaction, or financial arrangement.
-
E.
leftDeposits
Indicates that an entity has placed or left deposits (such as money or resources) with another entity or at a particular location.
- F. None of above. chosen
Provenance (4 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a849f4481908de0e3bc4f61da1c |
completed | May 2, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6142a0b988190b404d078f73c3cb9 |
completed | May 2, 2026, 3:11 p.m. |
Created at: April 27, 2026, 4:31 a.m.