Triple
T16977488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isa ibn Maryam |
E411849
|
entity |
| Predicate | willReturnAccordingTo |
P72263
|
FINISHED |
| Object | Islamic eschatology |
—
|
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: Islamic eschatology | Statement: [Isa ibn Maryam, willReturnAccordingTo, Islamic eschatology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: willReturnAccordingTo Context triple: [Isa ibn Maryam, willReturnAccordingTo, Islamic eschatology]
-
A.
mockedBy
Indicates that one entity ridicules, teases, or makes fun of another entity.
-
B.
returnProphecy
Indicates that an entity gives back or delivers a previously received prophecy to its original source or rightful recipient.
-
C.
willReturnBeforeDayOfJudgment
chosen
Indicates that the subject is expected to come back or reappear at some time prior to the Day of Judgment.
-
D.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified entity.
-
E.
setsExpectationsFor
Indicates that one entity defines or communicates standards, requirements, or anticipated outcomes that another entity is expected to meet or follow.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d184f2cc81908ac629c8f87696f8 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.