Triple
T25117431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uspanteko people |
E629165
|
entity |
| Predicate | hasCommunityAuthorities |
P98352
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Uspanteko people, hasCommunityAuthorities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityAuthorities Context triple: [Uspanteko people, hasCommunityAuthorities, yes]
-
A.
hasRoleInCommunity
Indicates that an entity holds or performs a specific role, function, or position within a particular community.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasCommunityControl
chosen
Indicates that authority or decision-making power over something is held collectively by a local community or community-based group.
-
D.
canBeConferredByCommunity
Indicates that something (such as a status, right, or benefit) may be granted or bestowed through a decision or action taken by a community.
-
E.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 18, 2026, 6:27 a.m.