Triple
T30769668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ximoluo |
E783480
|
entity |
| Predicate | socialGrouping |
P34598
|
FINISHED |
| Object | ethnolinguistic group |
—
|
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: ethnolinguistic group | Statement: [Ximoluo, socialGrouping, ethnolinguistic group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialGrouping Context triple: [Ximoluo, socialGrouping, ethnolinguistic group]
-
A.
socialGroupInvolved
Indicates that a particular social group participates in, is affected by, or is otherwise involved in the specified event or situation.
-
B.
hasSocialGroup
chosen
Indicates that an entity belongs to, is associated with, or participates in a particular social group or community.
-
C.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
D.
socialGroupBenefited
Indicates that a particular social group gains an advantage, improvement, or positive impact as a result of an action, event, or resource.
-
E.
groupTogether
Indicates that multiple entities are treated or arranged as a single collective unit or set.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 29, 2026, 8:40 p.m.