Triple
T35468756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rexburg Idaho Temple |
E1025150
|
entity |
| Predicate | hasBaptistry |
P55197
|
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: [Rexburg Idaho Temple, hasBaptistry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaptistry Context triple: [Rexburg Idaho Temple, hasBaptistry, yes]
-
A.
hasBaptistery
chosen
Indicates that an entity includes, contains, or is associated with a baptistery as part of its structure or facilities.
-
B.
baptismPlace
Indicates the place where an individual was baptized.
-
C.
baptismAssociatedWith
Indicates a relationship in which an entity is connected or related to a baptism event, such as by participation, performance, location, or contextual association.
-
D.
hasSacristy
Indicates that a religious building includes or is associated with a sacristy (a room where sacred vessels, vestments, and liturgical items are kept and prepared).
-
E.
hasBasilica
Indicates that one entity possesses, contains, or is associated with a basilica as a significant feature or component.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:04 p.m.