Triple
T3623455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sayyid dynasty |
E76780
|
entity |
| Predicate | territorialCore |
P13519
|
FINISHED |
| Object | Delhi region |
—
|
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: Delhi region | Statement: [Sayyid dynasty, territorialCore, Delhi region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territorialCore Context triple: [Sayyid dynasty, territorialCore, Delhi region]
-
A.
coreTerritoryAround
Indicates that one entity serves as the central or primary territory surrounding or enclosing another entity.
-
B.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
C.
wasCoreTerritoryOf
chosen
Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
-
D.
partitionedTerritory
Indicates that a larger territory has been divided into distinct parts or regions, typically with defined boundaries or administrative separation.
-
E.
territorialExtent
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2bc79008190abe6900adcbda8de |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.