Triple
T18312599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motutapu Island Marine Reserve |
E438664
|
entity |
| Predicate | miningAllowed |
P131289
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Motutapu Island Marine Reserve, miningAllowed, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miningAllowed Context triple: [Motutapu Island Marine Reserve, miningAllowed, no]
-
A.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
B.
miningStarted
Indicates that the process of extracting resources from a source or site has begun.
-
C.
connectsToMiningRegion
Indicates a relationship where something is physically or functionally linked to a mining region, such as through infrastructure, operations, or direct access.
-
D.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
-
E.
hasMiningArea
Indicates that an entity possesses, controls, or is associated with a designated area where mining activities take place.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5021a96b48190976273be3ff3e5c6 |
completed | April 19, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:36 a.m.