Triple
T7152076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panguna mine |
E166714
|
entity |
| Predicate | secondaryProduct |
P65738
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [Panguna mine, secondaryProduct, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryProduct Context triple: [Panguna mine, secondaryProduct, gold]
-
A.
secondaryProducts
chosen
Indicates that certain entities arise as secondary or byproduct outputs from a primary process, activity, or production.
-
B.
secondMajorProduct
Indicates that an entity is the second most important or second primary product associated with another entity (such as a company, brand, or producer).
-
C.
secondaryBrand
Indicates that one brand is a subordinate, supporting, or less prominent brand in relation to a primary brand.
-
D.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
E.
secondaryCustomer
Indicates a relationship where one customer is designated as an additional or subordinate customer associated with a primary customer in a given context.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f3e4a88190a3110f2368262528 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.