Triple
T7152107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panguna mine |
E166714
|
entity |
| Predicate | hasResourceEstimate |
P75155
|
FINISHED |
| Object | large copper reserves |
—
|
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: large copper reserves | Statement: [Panguna mine, hasResourceEstimate, large copper reserves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResourceEstimate Context triple: [Panguna mine, hasResourceEstimate, large copper reserves]
-
A.
estimatedUsing
Indicates that one entity’s value, state, or outcome is derived by applying an estimation method, model, or procedure based on another entity.
-
B.
areEstimatedIn
Indicates that a value or quantity is approximated or inferred within a specified context, framework, or unit.
-
C.
hasResourceBase
Indicates that one entity possesses, is founded on, or derives from another entity serving as its fundamental resource or base.
-
D.
hasEstimatedOriginalVolume
Indicates that an entity is associated with an approximate or calculated value for its original volume.
-
E.
hasResourcePotential
Indicates that an entity possesses the capacity or suitability to provide, generate, or support a particular resource in the future.
- 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_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. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:46 p.m.