Triple
T25068385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Suns |
E627843
|
entity |
| Predicate | fifthSunProphesiedToEndBy |
P22416
|
FINISHED |
| Object | earthquakes |
—
|
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: earthquakes | Statement: [Five Suns, fifthSunProphesiedToEndBy, earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fifthSunProphesiedToEndBy Context triple: [Five Suns, fifthSunProphesiedToEndBy, earthquakes]
-
A.
prophecyMade
Indicates that a prophetic statement or prediction has been declared by one entity concerning a future event or outcome involving another entity.
-
B.
subjectOfProphecy
chosen
Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
-
C.
fifthInstallmentReleaseYear
Indicates the calendar year in which the fifth installment of a series was released.
-
D.
isFifthKnownSatelliteOf
Indicates that one object is the fifth discovered or identified natural satellite (moon) of another celestial body.
-
E.
saidToBeTheLast
Indicates that something or someone is claimed or reported to be the final instance or member in a sequence, series, or group.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:10 a.m.