Triple
T27601041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apatit |
E700043
|
entity |
| Predicate | usesOreType |
P110138
|
FINISHED |
| Object | apatite-nepheline ore |
—
|
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: apatite-nepheline ore | Statement: [Apatit, usesOreType, apatite-nepheline ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesOreType Context triple: [Apatit, usesOreType, apatite-nepheline ore]
-
A.
receivesIronOreFrom
Indicates that one entity obtains or is supplied with iron ore from another entity.
-
B.
primaryOreTypes
Indicates the main types of ore that are predominantly associated with or extracted from a given entity.
-
C.
fuelSourceForSmelting
Indicates that one entity serves as the fuel used to generate heat for smelting another entity.
-
D.
hasTypeOfOreDeposit
chosen
Indicates that an entity possesses or is associated with a specific type of ore deposit.
-
E.
usesProductionResourcesOf
Indicates that one entity makes use of the production resources (such as facilities, equipment, or infrastructure) that belong to or are operated 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63096763c8190befb3934bfdc9350 |
completed | May 2, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:08 p.m.