Triple
T27601042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apatit |
E700043
|
entity |
| Predicate | endUseOfProducts |
P162733
|
FINISHED |
| Object | mineral fertilizers |
—
|
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: mineral fertilizers | Statement: [Apatit, endUseOfProducts, mineral fertilizers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endUseOfProducts Context triple: [Apatit, endUseOfProducts, mineral fertilizers]
-
A.
industrialUseEnd
Indicates the point in time or condition at which an industrial use or application of something is terminated or ceases.
-
B.
usedForProduct
Indicates that one entity serves as a tool, component, or means specifically employed in the creation, operation, or delivery of another entity considered as a product.
-
C.
productsUsedIn
Indicates that certain products are utilized or applied within a particular process, context, or entity.
-
D.
marketUseEnd
Indicates the point in time or condition at which the use of something in a market context ceases or is no longer valid.
-
E.
approximateEndUse
Indicates that something is an estimated or inferred final purpose, application, or consumption context of another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:08 p.m.