Triple
T38312260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berau Regency |
E1033720
|
entity |
| Predicate | hasLocalEthnicGroups |
P115409
|
FINISHED |
| Object | Dayak peoples |
—
|
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: Dayak peoples | Statement: [Berau Regency, hasLocalEthnicGroups, Dayak peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalEthnicGroups Context triple: [Berau Regency, hasLocalEthnicGroups, Dayak peoples]
-
A.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
-
B.
ethnicGroupsIncluded
Indicates that certain ethnic groups are encompassed, represented, or counted within a specified larger group, category, or context.
-
C.
hasEthnolinguisticPresence
chosen
Indicates that a particular ethnolinguistic group is present or represented within a specified place, context, or population.
-
D.
hasRecognizedEthnicGroup
Indicates that an entity includes or is associated with an ethnic group that is officially or socially recognized as distinct.
-
E.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.