Triple
T1760703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Ar-Rum |
E38650
|
entity |
| Predicate | containsProphecy |
P20088
|
FINISHED |
| Object | Prediction of Roman victory after defeat |
—
|
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: Prediction of Roman victory after defeat | Statement: [Surah Ar-Rum, containsProphecy, Prediction of Roman victory after defeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsProphecy Context triple: [Surah Ar-Rum, containsProphecy, Prediction of Roman victory after defeat]
-
A.
containsProphecyAbout
chosen
Indicates that one entity includes or conveys a prediction or foretelling specifically concerning another entity.
-
B.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
C.
usedToBeCalled
Indicates that an entity previously had a different name or title than the one it currently has.
-
D.
prophecyHeardBy
Indicates that a prophecy was heard or received by a particular entity.
-
E.
prophecyOverheardBy
Indicates that a prophecy was heard or accidentally listened to by a particular entity, without necessarily being its intended recipient.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab173936b4819097332ee185996bbd |
completed | March 6, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69aa61c9e06c819085489e00cfe72153 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.