Triple
T25100900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan of the Saints |
E628717
|
entity |
| Predicate | culturalRegionOfUse |
P1968
|
FINISHED |
| Object | South Asia |
E6055
|
NE 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: South Asia | Statement: [Sultan of the Saints, culturalRegionOfUse, South Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalRegionOfUse Context triple: [Sultan of the Saints, culturalRegionOfUse, South Asia]
-
A.
culturalRegion
chosen
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
B.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
-
C.
usedCulture
Indicates that one entity employed, applied, or drew upon the cultural practices, norms, or artifacts associated with another entity.
-
D.
countryOrRegionOfPrevalence
Indicates the country or geographic region where something (such as a condition, practice, or phenomenon) is most commonly found or occurs most frequently.
-
E.
usedInCountryOrRegion
Indicates that something (such as an item, concept, or practice) is utilized or applied within a specified country or region.
- F. None of above.
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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10489fdba481908e3f14f1fa2e98ae |
completed | May 22, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 6:25 a.m.