Triple
T6576876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaxabu language |
E157187
|
entity |
| Predicate | usedByCommunityFor |
P7159
|
FINISHED |
| Object | cultural practices |
—
|
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: cultural practices | Statement: [Kaxabu language, usedByCommunityFor, cultural practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByCommunityFor Context triple: [Kaxabu language, usedByCommunityFor, cultural practices]
-
A.
usedByCommunity
chosen
Indicates that something is utilized or adopted collectively by a particular community.
-
B.
usedInCommunity
Indicates that something is employed, practiced, or applied within a particular community or communal context.
-
C.
celebratedByCommunity
Indicates that an event, person, or achievement is honored, recognized, or joyfully acknowledged by a community.
-
D.
developedInCommunity
Indicates that something was created, built, or advanced through the participation, collaboration, or support of a particular community.
-
E.
communityOwned
Indicates that something is collectively owned, managed, or controlled by a community rather than by an individual or private 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_69c6882b3a108190b3a9eb343ae4162c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:54 p.m.