Triple
T35247941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | So |
E1018018
|
entity |
| Predicate | nationalityDistribution |
P57855
|
FINISHED |
| Object | Thai citizens |
—
|
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: Thai citizens | Statement: [So, nationalityDistribution, Thai citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalityDistribution Context triple: [So, nationalityDistribution, Thai citizens]
-
A.
citizenshipDistribution
chosen
Indicates how citizenship status or national affiliation is distributed across a set of individuals or groups.
-
B.
nationalityInWorld
Indicates that an entity has a specific national affiliation or citizenship within the world context.
-
C.
populationShareOfCountry
Indicates the proportion of a country’s total population that is accounted for by a specified subpopulation or region.
-
D.
populationDistributionCountry
Indicates how a country’s population is spread or allocated across its internal regions, groups, or categories.
-
E.
nationalityInHumanWorld
Indicates that one entity has the specified national affiliation or citizenship within the context of the human world.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 3, 2026, 4:02 p.m.