Triple
T7527007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bent’s Fort, Colorado |
E177918
|
entity |
| Predicate | openedAsTradingPost |
P67026
|
FINISHED |
| Object | 1833 |
—
|
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: 1833 | Statement: [Bent’s Fort, Colorado, openedAsTradingPost, 1833]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsTradingPost Context triple: [Bent’s Fort, Colorado, openedAsTradingPost, 1833]
-
A.
openedForTrade
chosen
Indicates that an entity has begun allowing commercial transactions or trading activities to occur.
-
B.
exclusiveTradingPostOf
Indicates a trading post that is dedicated to and used exclusively by a specific entity, with no other entities sharing its use.
-
C.
openingAuction
Indicates that an entity participates in, is associated with, or is defined in the context of an opening auction event or process.
-
D.
tradeSystem
Indicates a system or framework through which goods, services, or assets are exchanged between parties under defined rules or mechanisms.
-
E.
tradedTo
Indicates that ownership or contractual rights to an entity (such as a player, asset, or item) were transferred from one party to another, typically as part of an exchange or deal.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81cc5748190818443c48c9e3114 |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.