Triple
T4831094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Laramie |
E107946
|
entity |
| Predicate | establishedAsTradingPost |
P5762
|
FINISHED |
| Object | 1834 |
—
|
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: 1834 | Statement: [Fort Laramie, establishedAsTradingPost, 1834]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsTradingPost Context triple: [Fort Laramie, establishedAsTradingPost, 1834]
-
A.
historicTradeRole
Indicates that an entity historically functioned as a significant participant or hub in trade or commercial exchange.
-
B.
establishedAs
chosen
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
C.
historicalPeriodOfIntenseTrade
Indicates a time span characterized by unusually high levels of trade activity between parties or regions.
-
D.
tradedSince
Indicates that an entity has been actively traded starting from a specified point in time and continuing thereafter.
-
E.
establishedThrough
Indicates that a relationship, structure, or state comes into existence or is formally created by means of a specified process, action, or intermediary.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.