Triple
T25291189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ridanieh |
E634086
|
entity |
| Predicate | sovereignStateBefore |
P158354
|
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: [Battle of Ridanieh, sovereignStateBefore, Mamluk Sultanate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovereignStateBefore Context triple: [Battle of Ridanieh, sovereignStateBefore, Mamluk Sultanate]
-
A.
sovereignStateAfter
Indicates that one sovereign state succeeds another as its political or legal successor in time.
-
B.
sovereignStateUntil
Indicates that an entity functioned as a sovereign state up to a specified end time or date.
-
C.
sovereignState
Indicates that an entity is recognized as an independent, self-governing state with ultimate authority over its territory and not subject to any higher political power.
-
D.
sovereignStateDuring
Indicates that one entity functioned as the sovereign state governing another entity during a specified time period.
-
E.
hasSovereignState
Indicates that one entity is the sovereign state that has ultimate authority or jurisdiction over 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fcc8fe88190bf330715354553f6 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:22 p.m.