Triple
T31135119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of the Community of Christ |
E793616
|
entity |
| Predicate | officialCenter |
P38076
|
FINISHED |
| Object | Community of Christ Temple |
—
|
NE NERFINISHED |
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: Community of Christ Temple | Statement: [President of the Community of Christ, officialCenter, Community of Christ Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialCenter Context triple: [President of the Community of Christ, officialCenter, Community of Christ Temple]
-
A.
mainOffice
chosen
Indicates that one location or office serves as the primary or central office for an organization or entity.
-
B.
officialRepositoryFor
Indicates that one entity serves as the primary, authoritative repository or source for another entity.
-
C.
formsCenterOf
Indicates that one entity constitutes the central or core part of another entity.
-
D.
adminCenterLocatedOn
Indicates that the administrative center of an entity is situated on or within a specified geographic or physical feature.
-
E.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: April 29, 2026, 9:05 p.m.