Triple
T29858088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paraguayan diaspora |
E758243
|
entity |
| Predicate | regionConcentratedIn |
P70368
|
FINISHED |
| Object | South 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: South America | Statement: [Paraguayan diaspora, regionConcentratedIn, South America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionConcentratedIn Context triple: [Paraguayan diaspora, regionConcentratedIn, South America]
-
A.
hasPopulationConcentrationIn
chosen
Indicates that a population is densely or significantly clustered within a specified geographic area or region.
-
B.
concentratedInProvince
Indicates that something is primarily located, focused, or densely present within a particular province.
-
C.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
D.
concentratedInCountry
Indicates that the majority or primary presence of something (such as activity, resources, or focus) is located within a specific country.
-
E.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 29, 2026, 5:47 p.m.