Triple
T27616385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temples of The Church of Jesus Christ of Latter-day Saints |
E700447
|
entity |
| Predicate | earlyKeyTemple |
P49309
|
FINISHED |
| Object | Nauvoo Temple |
—
|
NE NERFINISHED |
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: Nauvoo Temple | Statement: [Temples of The Church of Jesus Christ of Latter-day Saints, earlyKeyTemple, Nauvoo Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyKeyTemple Context triple: [Temples of The Church of Jesus Christ of Latter-day Saints, earlyKeyTemple, Nauvoo Temple]
-
A.
earlyTempleLocation
Indicates that a temple or religious structure was located at a particular place during an early or initial historical period.
-
B.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
C.
templeOpening
Indicates that a temple begins operating or becomes accessible for worship, visitation, or related activities.
-
D.
startingTemple
chosen
Indicates that an entity serves as the initial or origin temple associated with another entity or process.
-
E.
earlierTomb
Indicates that one tomb chronologically predates another tomb.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 2:12 p.m.