Triple
T32923111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Fifty |
E842194
|
entity |
| Predicate | afterDeathOfFounder |
P61767
|
FINISHED |
| Object | continued under Brigham Young |
—
|
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: continued under Brigham Young | Statement: [Council of Fifty, afterDeathOfFounder, continued under Brigham Young]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterDeathOfFounder Context triple: [Council of Fifty, afterDeathOfFounder, continued under Brigham Young]
-
A.
afterDeathOfFounderLedBy
chosen
Indicates that an organization or group came under the leadership of a specified entity following the death of its founder.
-
B.
foundedAfterDeathOf
Indicates that the founding of one entity occurred only after the death of another entity.
-
C.
afterDeathOf
Indicates that one event, state, or condition occurs subsequent to and as a result of the death of a specified entity.
-
D.
founderDiedIn
Indicates that the person who founded an entity died in a specified place or at a specified time.
-
E.
hasFormerFounder
Indicates that an entity was previously a founder of another entity but no longer holds that founder role or status.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:20 a.m.