Triple
T8010053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhammad al-Mahdi |
E186464
|
entity |
| Predicate | minorOccultationStart |
P80546
|
FINISHED |
| Object | 874 CE |
—
|
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: 874 CE | Statement: [Muhammad al-Mahdi, minorOccultationStart, 874 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minorOccultationStart Context triple: [Muhammad al-Mahdi, minorOccultationStart, 874 CE]
-
A.
hasBeenObservedByOccultation
Indicates that an object or phenomenon has been detected or studied through an occultation event, where it is temporarily obscured by another body.
-
B.
observedAstronomicalEvent
Indicates that an entity has witnessed, detected, or recorded a specific astronomical event.
-
C.
marksAstronomicalEvent
Indicates that one entity serves as a sign, boundary, or reference point denoting the occurrence or timing of an astronomical event.
-
D.
meteoroidSource
Indicates that one entity is the origin or source from which the meteoroid represented by the other entity comes.
-
E.
obscuredIn
Indicates that one entity is hidden, blocked, or made less visible due to the presence or influence of another entity.
- F. None of above. chosen
Provenance (4 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d70caf8819090a9f98025470c0d |
completed | March 31, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:19 p.m.