Triple
T22158178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hetian jade |
E547595
|
entity |
| Predicate | mainMineralComponent |
P45236
|
FINISHED |
| Object | actinolite |
—
|
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: actinolite | Statement: [Hetian jade, mainMineralComponent, actinolite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainMineralComponent Context triple: [Hetian jade, mainMineralComponent, actinolite]
-
A.
hasMineral
chosen
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
B.
hasImportantMineral
Indicates that an entity contains or is associated with a mineral considered significant or valuable in a given context.
-
C.
typeOfMineralsCovered
Indicates that one entity specifies or lists the kinds or categories of minerals that are included, addressed, or affected by another entity.
-
D.
mineralGroup
Indicates that one entity is classified as a member or subtype of a particular mineral group defined by shared mineralogical characteristics.
-
E.
typeOfMineralProduced
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12a2aadb48190b4d739d1df9529db |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.