Triple
T34949573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norseman, Western Australia |
E1007951
|
entity |
| Predicate | discoveryOfGold |
P62321
|
FINISHED |
| Object | 1890s |
—
|
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: 1890s | Statement: [Norseman, Western Australia, discoveryOfGold, 1890s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryOfGold Context triple: [Norseman, Western Australia, discoveryOfGold, 1890s]
-
A.
goldDiscovered
chosen
Indicates that an instance of gold has been found or identified at a particular time, place, or context.
-
B.
discoveryOfOre
Indicates the event or relationship in which a particular ore deposit is found, identified, or recognized, typically linking the discoverer, the ore, and the location or time of discovery.
-
C.
goldRushEra
Indicates a relationship or context tied to the historical period characterized by intense migration and mining activity driven by newly discovered gold.
-
D.
startOfGoldRush
Indicates that the subject marks the beginning or initial occurrence of a gold rush event.
-
E.
eraOfDiscovery
Indicates a relationship where something belongs to, occurs in, or is characteristic of a specific era of discovery or exploration.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4 p.m.