Triple
T26976888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuinga |
E679481
|
entity |
| Predicate | hasSocialGrouping |
P34598
|
FINISHED |
| Object | ethnic community |
—
|
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: ethnic community | Statement: [Kuinga, hasSocialGrouping, ethnic community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialGrouping Context triple: [Kuinga, hasSocialGrouping, ethnic community]
-
A.
hasSocialGroup
chosen
Indicates that an entity belongs to, is associated with, or participates in a particular social group or community.
-
B.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
-
C.
hasCommunityGroups
Indicates that an entity is associated with one or more organized community groups or organizations.
-
D.
hasPopulationGrouping
Indicates a relationship where an entity is associated with a specific categorization or grouping of its population (e.g., by size, type, or demographic characteristics).
-
E.
hasCollaborativeGroup
Indicates that an entity participates in or is associated with a collaborative group formed to work together toward shared goals or activities.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 6:43 a.m.