Triple
T24800664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enrekang people |
E620513
|
entity |
| Predicate | ethnoRegionalGroupOf |
P5147
|
FINISHED |
| Object | South Sulawesi |
—
|
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 Sulawesi | Statement: [Enrekang people, ethnoRegionalGroupOf, South Sulawesi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnoRegionalGroupOf Context triple: [Enrekang people, ethnoRegionalGroupOf, South Sulawesi]
-
A.
ethnicGroupBase
Indicates that one entity serves as the primary or foundational ethnic group from which another entity is derived, associated, or defined.
-
B.
ethnolinguisticGroups
Indicates a relationship where groups are categorized or associated based on shared ethnic and linguistic characteristics.
-
C.
regionalGrouping
chosen
Indicates that entities are organized or associated together based on shared geographic or regional characteristics.
-
D.
ethnoLinguisticRegionOf
Indicates that a region is defined or characterized by the shared ethnic and linguistic identity of the group associated with it.
-
E.
ethnicGroupOn
Indicates that a particular ethnic group is present on, associated with, or resides in a specified place or entity.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f412a9b64881908ed86b9c9b044635 |
completed | May 1, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:49 a.m.