Triple
T8990181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minbar of the Prophet |
E214767
|
entity |
| Predicate | hasLaterUsers |
P47020
|
FINISHED |
| Object | successive imams of Al-Masjid an-Nabawi |
—
|
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: successive imams of Al-Masjid an-Nabawi | Statement: [Minbar of the Prophet, hasLaterUsers, successive imams of Al-Masjid an-Nabawi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterUsers Context triple: [Minbar of the Prophet, hasLaterUsers, successive imams of Al-Masjid an-Nabawi]
-
A.
hasUser
Indicates that an entity is associated with or linked to a specific user.
-
B.
someMembersLater
Indicates that at least some members of a group or set occur, appear, or hold a property at a later time relative to another reference point or group.
-
C.
hasSubsequent
chosen
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
D.
hasLaterTitle
Indicates that one title occurs chronologically after another title in a sequence or timeline.
-
E.
notEarlierThan
Indicates that one event, time, or state does not occur before another, i.e., it is simultaneous with or later than the referenced point.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc68733548819096a5ba0ff41e43da |
completed | April 1, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:04 p.m.