Triple
T9171074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plates of Ether |
E220079
|
entity |
| Predicate | timeFrameClaimed |
P9416
|
FINISHED |
| Object | post-Babel to pre-Nephite era |
—
|
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: post-Babel to pre-Nephite era | Statement: [Plates of Ether, timeFrameClaimed, post-Babel to pre-Nephite era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeFrameClaimed Context triple: [Plates of Ether, timeFrameClaimed, post-Babel to pre-Nephite era]
-
A.
timeframeClaimedForSingularity
Indicates that an entity asserts or specifies a particular period of time in which a technological or singularity event is expected to occur.
-
B.
timeFrameSpecified
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
C.
timePeriodProposed
chosen
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
- 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.