Triple
T20412115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Ashraf Qansuh al-Ghawri |
E500610
|
entity |
| Predicate | reignStartDetail |
P1506
|
FINISHED |
| Object | 1501 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: 1501 CE | Statement: [Al-Ashraf Qansuh al-Ghawri, reignStartDetail, 1501 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStartDetail Context triple: [Al-Ashraf Qansuh al-Ghawri, reignStartDetail, 1501 CE]
-
A.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
B.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
C.
reignStartBefore
Indicates that the start of one entity’s reign occurs earlier in time than the start of another entity’s reign.
-
D.
reignAsHeirStart
Indicates the point in time when an individual begins exercising authority or functions in the role of heir, marking the start of their effective reign as designated successor.
-
E.
reignAsRegentStart
Indicates the point in time when an individual begins exercising ruling authority as a regent on behalf of another.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a3f8fdc8190b05b6c41b38f34b7 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.