Triple
T32783214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bawean Malay |
E838412
|
entity |
| Predicate | hasMigrationCommunity |
P17132
|
FINISHED |
| Object | Baweanese diaspora in Malaysia |
—
|
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: Baweanese diaspora in Malaysia | Statement: [Bawean Malay, hasMigrationCommunity, Baweanese diaspora in Malaysia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMigrationCommunity Context triple: [Bawean Malay, hasMigrationCommunity, Baweanese diaspora in Malaysia]
-
A.
hasCommunityIn
chosen
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
B.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
-
C.
hasCommunitySupport
Indicates that an entity is backed, endorsed, or positively received by a community or group of users.
-
D.
hasTargetCommunity
Indicates that something is specifically intended for, directed toward, or designed to serve a particular community or group.
-
E.
hasGlobalCommunity
Indicates that an entity is associated with or participates in a worldwide community or network of people.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 1, 2026, 1:14 a.m.