Triple
T26969016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shamsuddin Muzaffar Shah |
E679253
|
entity |
| Predicate | dynastyDuration |
P160362
|
FINISHED |
| Object | short-lived |
—
|
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: short-lived | Statement: [Shamsuddin Muzaffar Shah, dynastyDuration, short-lived]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyDuration Context triple: [Shamsuddin Muzaffar Shah, dynastyDuration, short-lived]
-
A.
dynastyFoundedDuration
chosen
Indicates the length of time between when a dynasty was founded and when it ceased to exist or lost its founding status.
-
B.
reignDuration
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
C.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
-
D.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
E.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 6:38 a.m.