Triple
T9334830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Jesus Christ of Latter-day Saints general conference |
E224617
|
entity |
| Predicate | numberOfSessionsPerYear |
P6891
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Church of Jesus Christ of Latter-day Saints general conference, numberOfSessionsPerYear, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSessionsPerYear Context triple: [Church of Jesus Christ of Latter-day Saints general conference, numberOfSessionsPerYear, 2]
-
A.
minimumSessionsPerYear
Indicates the smallest number of sessions that must occur within a one-year period.
-
B.
sessionCount
chosen
Indicates the number of distinct sessions associated with an entity or interaction context.
-
C.
typicalNumberOfMeetingsPerSeason
Indicates the usual or average count of meetings that occur within a single season.
-
D.
meetsBetweenSessionsOf
Indicates that one entity meets another during the interval between scheduled sessions or events.
-
E.
hasLegislativeSessionCount
Indicates the number of legislative sessions associated with a given legislative body, term, or jurisdiction.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37ee53988190bcc76588edbc2858 |
completed | April 1, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.