Triple
T13918516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultanates |
E334682
|
entity |
| Predicate | oftenSucceeded |
P112285
|
FINISHED |
| Object | caliphate provinces or emirates |
—
|
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: caliphate provinces or emirates | Statement: [Sultanates, oftenSucceeded, caliphate provinces or emirates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenSucceeded Context triple: [Sultanates, oftenSucceeded, caliphate provinces or emirates]
-
A.
oftenPrecededBy
Indicates that one event, state, or item commonly occurs or appears before another in time or sequence.
-
B.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
-
C.
oftenSays
Indicates that one entity frequently makes a particular statement or remark, or regularly expresses a certain idea or phrase.
-
D.
maySucceed
Indicates that one entity has the potential or possibility to follow or replace another in a role, position, or sequence.
-
E.
oftenStatedWith
Indicates that one statement, fact, or expression is frequently mentioned or asserted together with another.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de272753e48190bc609482635280ff |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:16 p.m.