Triple
T5490561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Lake Valley |
E123689
|
entity |
| Predicate | firstMormonSettlementYear |
P12156
|
FINISHED |
| Object | 1847 |
—
|
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: 1847 | Statement: [Salt Lake Valley, firstMormonSettlementYear, 1847]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMormonSettlementYear Context triple: [Salt Lake Valley, firstMormonSettlementYear, 1847]
-
A.
firstSettlersArrived
chosen
Indicates that the earliest group of settlers reached or came to a particular place or region.
-
B.
firstHermitSettlementCentury
Indicates the century during which the first hermit settlement associated with a given entity was established.
-
C.
firstPermanentSettler
Indicates that the subject is the earliest individual or group to establish a lasting, continuous residence in the location or entity specified by the object.
-
D.
firstMajorColonyFoundationYear
Indicates the year in which an entity’s earliest or primary major colony was founded.
-
E.
firstPermanentEuropeanSettlement
Indicates that the subject is the location of the earliest lasting European-established community in a given region 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927f198c8190889b555be9bf9765 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a8df6481908d1643f7342fe6f0 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.