Triple
T2185630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamluk Sultanate |
E49145
|
entity |
| Predicate | startOfBurjiPeriod |
P37169
|
FINISHED |
| Object | 1382 |
—
|
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: 1382 | Statement: [Mamluk Sultanate, startOfBurjiPeriod, 1382]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfBurjiPeriod Context triple: [Mamluk Sultanate, startOfBurjiPeriod, 1382]
-
A.
mainBurialsPeriodStart
Indicates the time period or date when the primary or main phase of burials at a site or within a context began.
-
B.
historicalMigrationPeriodStart
Indicates the point in time when a particular historical migration period begins.
-
C.
mainBurialsPeriodEnd
Indicates the time period or date when the primary phase of burials at a site or context came to an end.
-
D.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
E.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf9c77fc8190a323bcaf644fb2c5 |
completed | March 7, 2026, 6:03 a.m. |
Created at: March 4, 2026, 7:45 p.m.