Triple
T33624244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalal al-Din Masud Shah Inju |
E861355
|
entity |
| Predicate | cultureCenterRuled |
P162129
|
FINISHED |
| Object | Shiraz |
—
|
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: Shiraz | Statement: [Jalal al-Din Masud Shah Inju, cultureCenterRuled, Shiraz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultureCenterRuled Context triple: [Jalal al-Din Masud Shah Inju, cultureCenterRuled, Shiraz]
-
A.
countryRuled
Indicates that one entity exercises governing authority or political control over a country.
-
B.
historicalEmpireCenter
Indicates that a location served as the primary political or administrative center of a historical empire.
-
C.
importantDynastyCenterFor
chosen
Indicates that a location served as a significant political, cultural, or administrative center for a particular dynasty.
-
D.
historicalRegionOfInfluence
Indicates that one entity was historically within the geographic, political, or cultural sphere of influence of another entity.
-
E.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 1, 2026, 1:41 a.m.