Triple
T20292326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nauvoo Illinois Temple |
E510056
|
entity |
| Predicate | isTempleNumber |
P113872
|
FINISHED |
| Object | 113 |
—
|
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: 113 | Statement: [Nauvoo Illinois Temple, isTempleNumber, 113]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTempleNumber Context triple: [Nauvoo Illinois Temple, isTempleNumber, 113]
-
A.
isNumberedTempleOf
chosen
Indicates that one entity is a specific, designated temple identified by a particular number within a series or system associated with another entity.
-
B.
hasTempleCount
Indicates that an entity is associated with a specified number of temples.
-
C.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
D.
isActiveTemple
Indicates that a temple is currently functioning and in regular religious use, rather than being abandoned, ruined, or inactive.
-
E.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
- 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_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. |
Created at: April 16, 2026, 11:12 a.m.