Triple
T29521153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shompole Conservancy |
E748935
|
entity |
| Predicate | communityInvolved |
P6194
|
FINISHED |
| Object | Maasai |
—
|
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: Maasai | Statement: [Shompole Conservancy, communityInvolved, Maasai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityInvolved Context triple: [Shompole Conservancy, communityInvolved, Maasai]
-
A.
communityService
Indicates participation in activities intended to benefit or support a community, typically performed voluntarily or as a civic responsibility.
-
B.
community
chosen
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
C.
communityAspect
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
D.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
E.
communityMovement
Indicates a coordinated effort or shift undertaken collectively by members of a community toward a shared goal or change.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 4:41 p.m.