Triple
T9170919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mormon |
E220076
|
entity |
| Predicate | timePeriodInText |
P302
|
FINISHED |
| Object | approximately 4th century AD (Book of Mormon chronology) |
—
|
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: approximately 4th century AD (Book of Mormon chronology) | Statement: [Mormon, timePeriodInText, approximately 4th century AD (Book of Mormon chronology)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodInText Context triple: [Mormon, timePeriodInText, approximately 4th century AD (Book of Mormon chronology)]
-
A.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
timeDescribedAs
Indicates that a specific time or temporal interval is characterized, labeled, or expressed using a particular description or representation.
-
C.
timeToSentence
Indicates the amount of time that elapses from a relevant starting point (e.g., offense, arrest, or charge) until a formal sentence is imposed.
-
D.
timePeriodImplied
Indicates that a time period is inferred or implied by context rather than being explicitly specified.
-
E.
timePeriodRecognized
Indicates that a specific span of time has been formally identified or acknowledged as significant or valid within a given context.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaae38ee48190bf783477bc37913d |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.