Triple
T28577151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ProphetsInIslam |
E723273
|
entity |
| Predicate | includesProphet |
P88738
|
FINISHED |
| Object | AdamInIslam |
—
|
NE NERFINISHED |
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: AdamInIslam | Statement: [ProphetsInIslam, includesProphet, AdamInIslam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesProphet Context triple: [ProphetsInIslam, includesProphet, AdamInIslam]
-
A.
prophetAmong
chosen
Indicates that one entity serves as a prophet within, or in relation to, a particular group, community, or people represented by the other entity.
-
B.
followsProphet
Indicates that one entity accepts the guidance or teachings of, and adheres to the leadership or example set by, a prophet.
-
C.
linkedToProphet
Indicates a relationship in which an entity is associated or connected in some meaningful way to a prophet.
-
D.
prophecySource
Indicates that one entity is the origin or provider of a particular prophecy concerning another entity or event.
-
E.
prophecyMade
Indicates that a prophetic statement or prediction has been declared by one entity concerning a future event or outcome involving another entity.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: April 28, 2026, 4:13 a.m.