Triple
T25483459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dulkadirid beylik |
E638637
|
entity |
| Predicate | bufferBetween |
P4190
|
FINISHED |
| Object | Mamluk Sultanate |
—
|
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: Mamluk Sultanate | Statement: [Dulkadirid beylik, bufferBetween, Mamluk Sultanate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bufferBetween Context triple: [Dulkadirid beylik, bufferBetween, Mamluk Sultanate]
-
A.
bufferZone
chosen
Indicates the existence of an area or region that serves as a protective or separating space between two or more entities or activities.
-
B.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
C.
wasDemarcatedBetween
Indicates that a boundary or dividing line was formally established separating one entity from another.
-
D.
currentBetween
Indicates that the current value of a quantity lies within a specified range between two boundary values.
-
E.
gapBetween
Indicates the spatial or temporal distance or separation that exists between two entities.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f77942908190b993fdf300182952 |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:31 p.m.