Triple
T25003053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic historiography |
E625767
|
entity |
| Predicate | studiesEventType |
P119424
|
FINISHED |
| Object | rise and fall of dynasties |
—
|
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: rise and fall of dynasties | Statement: [Islamic historiography, studiesEventType, rise and fall of dynasties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiesEventType Context triple: [Islamic historiography, studiesEventType, rise and fall of dynasties]
-
A.
academicEventsInclude
Indicates that certain academic events are contained within, or form part of, a broader set or collection of academic events.
-
B.
individualEvents
Indicates that the subject is associated with one or more distinct, separately identifiable events rather than a single aggregated or continuous occurrence.
-
C.
appearsAtEventType
Indicates that an entity is present or participates in an event of a specified type.
-
D.
typeOfEvent
Indicates that one entity is classified as a specific kind or category of event.
-
E.
genreOfDescribedEvents
chosen
Indicates that one entity specifies the genre or type category of the events described by another entity.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:05 a.m.