Triple
T8634754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auraria, Colorado Territory |
E204492
|
entity |
| Predicate | mergedIn |
P77
|
FINISHED |
| Object | 1860 |
—
|
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: 1860 | Statement: [Auraria, Colorado Territory, mergedIn, 1860]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedIn Context triple: [Auraria, Colorado Territory, mergedIn, 1860]
-
A.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
B.
mergedInto
chosen
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
C.
mergedOrReorganized
Indicates that one entity has combined with or been structurally reorganized into another entity, resulting in a changed or unified organizational form.
-
D.
mergedInstitution
Indicates that one institution has combined with another to form a single, unified institution.
-
E.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.