Triple
T20292325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nauvoo Illinois Temple |
E510056
|
entity |
| Predicate | isSecondTempleOnSite |
P139562
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nauvoo Illinois Temple, isSecondTempleOnSite, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSecondTempleOnSite Context triple: [Nauvoo Illinois Temple, isSecondTempleOnSite, yes]
-
A.
firstTempleIn
Indicates that an entity is the earliest or original temple located in a specified place or region.
-
B.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
C.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
-
D.
isHistoricLDSTemple
Indicates that a temple is recognized as historically significant within the context of The Church of Jesus Christ of Latter-day Saints (LDS).
-
E.
nearbyBiblicalSites
Indicates that one or more biblical sites are located close to a given reference location or to each other.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e677024de08190bfa54ae26b5486d1 |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:12 a.m.