Triple
T628338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community of Christ Temple |
E15868
|
entity |
| Predicate | dedicatedIn |
P1273
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Community of Christ Temple, dedicatedIn, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedIn Context triple: [Community of Christ Temple, dedicatedIn, 1994]
-
A.
dedicated
Indicates that one entity is formally assigned, reserved, or committed for the specific use, benefit, or purpose of another entity.
-
B.
rededicatedBy
Indicates that something has been dedicated again or anew by a particular agent or entity.
-
C.
dedicationDate
chosen
Indicates the date on which something (such as a building, monument, or work) is formally dedicated or inaugurated.
-
D.
commissionedIn
Indicates that an entity was formally requested or authorized to be created, produced, or carried out in a specific time period or location.
-
E.
directed
Indicates that one entity served as the director or guiding authority responsible for overseeing and controlling the actions or production involving another entity.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e5b5a308190a62165f9275e2f5f |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49d01b29081908be87e4cd7726ff1 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.