Triple
T12315123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waihi |
E293579
|
entity |
| Predicate | establishedAsMiningTown |
P53613
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Waihi, establishedAsMiningTown, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsMiningTown Context triple: [Waihi, establishedAsMiningTown, late 19th century]
-
A.
foundedAsMiningTownIn
chosen
Indicates that a settlement or town was originally established as a mining town in the specified location or jurisdiction.
-
B.
isMiningTown
Indicates that a location is a town whose primary historical or economic basis is mining activities.
-
C.
foundedAsMiningCamp
Indicates that a settlement or town was originally established as a mining camp.
-
D.
wasMajorMiningTownInCentury
Indicates that a town was a significant center of mining activity during a specified century.
-
E.
wasRoyalMiningTownOf
Indicates that a town historically held official royal status and functioned as a designated center for mining activities under royal authority.
- 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.