Triple
T4021626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin Valley opal fields |
E91290
|
entity |
| Predicate | hasOpalType |
P53496
|
FINISHED |
| Object | precious black fire opal |
—
|
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: precious black fire opal | Statement: [Virgin Valley opal fields, hasOpalType, precious black fire opal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpalType Context triple: [Virgin Valley opal fields, hasOpalType, precious black fire opal]
-
A.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
B.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
C.
hasStandardType
Indicates that something conforms to or is categorized under a defined standard classification or type.
-
D.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
E.
hasRuntimeType
Indicates that an entity is of, or conforms to, a specific type when evaluated at runtime rather than at compile time.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefacb4c208190b8dd595a534850b2 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:35 p.m.