Triple
T9416447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panaca, Nevada |
E227031
|
entity |
| Predicate | isPredominantlyMormonCommunity |
P77999
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Panaca, Nevada, isPredominantlyMormonCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPredominantlyMormonCommunity Context triple: [Panaca, Nevada, isPredominantlyMormonCommunity, true]
-
A.
viewOfLDSChurch
Indicates a person's stance, opinion, or perspective regarding the Church of Jesus Christ of Latter-day Saints (LDS Church).
-
B.
hasNotableReligiousCommunity
chosen
Indicates that an entity is known for having a significant or prominent religious community associated with it.
-
C.
hasMemberChurchesIn
Indicates that an organization or group includes member churches that are located within a specified geographic area or jurisdiction.
-
D.
majorRegionOfWorship
Indicates the primary geographic region where a deity, religion, or cult is predominantly worshipped.
-
E.
hasMemberChurch
Indicates that a particular church is a constituent member of a larger religious organization, denomination, or church body.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68c9917481909f793a2a9efb2a75 |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.