Triple
T15778033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dogra dynasty of Jammu and Kashmir |
E382537
|
entity |
| Predicate | subcontinentRegion |
P117763
|
FINISHED |
| Object | Indian subcontinent |
—
|
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: Indian subcontinent | Statement: [Dogra dynasty of Jammu and Kashmir, subcontinentRegion, Indian subcontinent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subcontinentRegion Context triple: [Dogra dynasty of Jammu and Kashmir, subcontinentRegion, Indian subcontinent]
-
A.
isInSubcontinent
chosen
Indicates that one entity (typically a place or region) is geographically located within the boundaries of a specified subcontinent.
-
B.
countrySubregion
Indicates that a country is located within or belongs to a specific subregion of the world.
-
C.
foundedInSubcontinent
Indicates that an entity was founded or established within a specific geographic subcontinent.
-
D.
subregionOf
Indicates that one region is geographically or administratively contained within, and is a part of, another larger region.
-
E.
regionSub
Indicates that one region is a subregion or contained part of another, larger region.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05199cd8881909462462cec34d35a |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.