Triple
T36508175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otago goldfields |
E899824
|
entity |
| Predicate | laterMiningActivity |
P38710
|
FINISHED |
| Object | dredging on Clutha River |
—
|
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: dredging on Clutha River | Statement: [Otago goldfields, laterMiningActivity, dredging on Clutha River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterMiningActivity Context triple: [Otago goldfields, laterMiningActivity, dredging on Clutha River]
-
A.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
B.
laterActivity
chosen
Indicates that one activity occurs after another in time, establishing a temporal ordering between them.
-
C.
hasMiningActivityType
Indicates that an entity is associated with a specific type or category of mining activity.
-
D.
miningActivityEnd
Indicates the point in time or event at which a mining operation or activity ceases or is formally concluded.
-
E.
likelyMiningRegion
Indicates that a region is inferred or predicted to be suitable or probable for mining activities based on available evidence or characteristics.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00ac5654a0819090701f61a5802d64 |
completed | May 10, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_6a00ab94b5e881909e15d1342e5f43be |
completed | May 10, 2026, 4 p.m. |
Created at: May 3, 2026, 4:10 p.m.