Triple
T32921457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oliver Cowdery |
E842153
|
entity |
| Predicate | yearOfRejoining |
P47035
|
FINISHED |
| Object | 1848 |
—
|
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: 1848 | Statement: [Oliver Cowdery, yearOfRejoining, 1848]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfRejoining Context triple: [Oliver Cowdery, yearOfRejoining, 1848]
-
A.
rejoinedCountryYear
chosen
Indicates the year in which an entity re-entered or rejoined a particular country after having previously left or been separated from it.
-
B.
rejoinedCountry
Indicates that an entity has become part of a country again after having previously separated or left it.
-
C.
reestablishedInYear
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
D.
joinedLeagueOfNations
Indicates that an entity became a member of the League of Nations at some point in time.
-
E.
joinedInYear
Indicates that an entity became a member of, or started participating in, another entity (such as an organization, group, or institution) in a specified calendar year.
- 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_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 1, 2026, 1:19 a.m.