Triple
T2600976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maitreya |
E58341
|
entity |
| Predicate | prophesiedTo |
P22416
|
FINISHED |
| Object | Appear on Earth in the future |
—
|
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: Appear on Earth in the future | Statement: [Maitreya, prophesiedTo, Appear on Earth in the future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prophesiedTo Context triple: [Maitreya, prophesiedTo, Appear on Earth in the future]
-
A.
prophecyHeardBy
Indicates that a prophecy was heard or received by a particular 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.
prophecyOverheardBy
Indicates that a prophecy was heard or accidentally listened to by a particular entity, without necessarily being its intended recipient.
-
D.
madeMajorProphecyAt
Indicates that an entity delivered or pronounced a significant prophecy at a specific place or time.
-
E.
linkedToProphet
Indicates a relationship in which an entity is associated or connected in some meaningful way to a prophet.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd4587014819089f78e93adf2144c |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d4e8648190b612eb09aa085451 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.