Triple
T32118883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawatiya |
E820310
|
entity |
| Predicate | diasporaOriginRegion |
P148708
|
FINISHED |
| Object | Indian subcontinent |
—
|
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: Indian subcontinent | Statement: [Lawatiya, diasporaOriginRegion, Indian subcontinent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diasporaOriginRegion Context triple: [Lawatiya, diasporaOriginRegion, Indian subcontinent]
-
A.
countryOfDiaspora
Indicates the country in which a diaspora community originating from another place is located.
-
B.
regionOfDiaspora
chosen
Indicates the geographic area where a dispersed population from an original homeland is settled or concentrated.
-
C.
majorDiasporaCountry
Indicates that a country is a primary destination or host state for a significant diaspora population originating from another country.
-
D.
hasDiasporaOriginCountry
Indicates that an entity representing a diaspora community or group originates from, or traces its roots back to, a specified country.
-
E.
diasporaType
Indicates the specific kind or category of diaspora relationship that exists between a group and its place of origin.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b90aa5e081908629bb2c63b2c281 |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:28 a.m.