Triple
T12315125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waihi |
E293579
|
entity |
| Predicate | secondaryResourceExtracted |
P99998
|
FINISHED |
| Object | silver |
—
|
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: silver | Statement: [Waihi, secondaryResourceExtracted, silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryResourceExtracted Context triple: [Waihi, secondaryResourceExtracted, silver]
-
A.
secondaryResource
chosen
Indicates that a resource serves as a secondary, supporting, or auxiliary resource in relation to a primary one.
-
B.
resourceExtracted
Indicates that a resource has been obtained or taken from a source entity, typically through an extraction process.
-
C.
overseesExtractionOf
Indicates that one entity supervises, manages, or has responsibility for the process by which another entity is extracted or obtained.
-
D.
resourceExtractionPolicy
Indicates the rules or strategies governing how natural or material resources are extracted from a given area or source.
-
E.
discoveredResource
Indicates that an entity has found, identified, or uncovered a particular resource.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.