Triple
T6320521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otago |
E141724
|
entity |
| Predicate | goldRushPeriod |
P55101
|
FINISHED |
| Object | 1860s |
—
|
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: 1860s | Statement: [Otago, goldRushPeriod, 1860s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goldRushPeriod Context triple: [Otago, goldRushPeriod, 1860s]
-
A.
goldRushEra
chosen
Indicates a relationship or context tied to the historical period characterized by intense migration and mining activity driven by newly discovered gold.
-
B.
goldDiscovered
Indicates that an instance of gold has been found or identified at a particular time, place, or context.
-
C.
goldenAgeApproxEnd
Indicates the approximate time or period when a golden age or peak era comes to an end.
-
D.
historicalPeriodOfProsperity
Indicates a time span in which a society, region, or entity experienced notable economic growth, stability, and overall flourishing.
-
E.
roleInGoldRush
Indicates that an entity played a specific role or had a particular involvement in the historical event known as the Gold Rush.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c61f008190b316b9ff1023b057 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.