Triple
T36760534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspen mining district |
E908182
|
entity |
| Predicate | timeOfMajorSettlement |
P116089
|
FINISHED |
| Object | early 1880s |
—
|
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: early 1880s | Statement: [Aspen mining district, timeOfMajorSettlement, early 1880s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMajorSettlement Context triple: [Aspen mining district, timeOfMajorSettlement, early 1880s]
-
A.
historicalPeriodOfSettlement
chosen
Indicates the historical time period during which a particular settlement or habitation of a place occurred.
-
B.
beganMajorSettlement
Indicates that an entity initiated the establishment of a significant, long-term settlement at a particular place or time.
-
C.
timeOfMajorBattle
Indicates the specific time at which a major battle took place.
-
D.
periodOfMajorRemains
Indicates the historical time period during which the primary surviving remains or artifacts associated with something were created or are dated.
-
E.
timeOfEarlySettlement
Indicates the specific time or period when an early settlement or resolution of an obligation, dispute, or transaction occurs.
- 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 3, 2026, 4:12 p.m.