Triple
T10111985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far West, Missouri |
E218261
|
entity |
| Predicate | datePlannedTempleCornerstonesLaid |
P92246
|
FINISHED |
| Object | July 4, 1838 |
—
|
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: July 4, 1838 | Statement: [Far West, Missouri, datePlannedTempleCornerstonesLaid, July 4, 1838]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datePlannedTempleCornerstonesLaid Context triple: [Far West, Missouri, datePlannedTempleCornerstonesLaid, July 4, 1838]
-
A.
cornerstoneLaidBy
Indicates that the act of laying a building’s cornerstone was performed by a specified agent or entity.
-
B.
templeConstruction
Indicates the action or process of building, erecting, or establishing a temple or similar sacred structure.
-
C.
templeOpening
Indicates that a temple begins operating or becomes accessible for worship, visitation, or related activities.
-
D.
lastMajorTempleClosed
Indicates the time or event at which the final significant temple associated with an entity was permanently closed.
-
E.
churchConstructionDate
Indicates the date on which a church was constructed or originally built.
- F. None of above. chosen
Provenance (4 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd15d1fd081908c6f6b021e3999da |
completed | April 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:03 p.m.