Triple
T27268173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajesh |
E687964
|
entity |
| Predicate | commonInDiasporaRegion |
P148708
|
FINISHED |
| Object | North America |
—
|
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: North America | Statement: [Rajesh, commonInDiasporaRegion, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonInDiasporaRegion Context triple: [Rajesh, commonInDiasporaRegion, North America]
-
A.
regionOfDiaspora
chosen
Indicates the geographic area where a dispersed population from an original homeland is settled or concentrated.
-
B.
countryOfDiaspora
Indicates the country in which a diaspora community originating from another place is located.
-
C.
majorDiasporaCountry
Indicates that a country is a primary destination or host state for a significant diaspora population originating from another country.
-
D.
hasDiasporaInfluenceOn
Indicates that a diaspora community exerts cultural, social, economic, or political influence on another entity, such as a country, region, or group.
-
E.
hasDiasporaOriginCountry
Indicates that an entity representing a diaspora community or group originates from, or traces its roots back to, a specified country.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 10:57 a.m.