Triple
T9050817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Periods of Revelation |
E216877
|
entity |
| Predicate | firstPeriodName |
P38737
|
FINISHED |
| Object | First Period of Revelation |
—
|
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: First Period of Revelation | Statement: [Three Periods of Revelation, firstPeriodName, First Period of Revelation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPeriodName Context triple: [Three Periods of Revelation, firstPeriodName, First Period of Revelation]
-
A.
firstStageName
chosen
Indicates that one entity is the initial or earliest stage name associated with another entity in a sequence or lifecycle.
-
B.
previousNamePeriod
Indicates the time span during which an entity was known by a former name before changing to its current name.
-
C.
firstGenerationName
Indicates that the specified name is assigned to or associated with the first generation in a sequence, lineage, or series.
-
D.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
-
E.
firstYear
Indicates that an entity is in its first year of existence, operation, or participation within a specified 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b54423081908d9fd985109e336a |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:10 p.m.