Triple
T33050954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umoja |
E845718
|
entity |
| Predicate | isEncouragedThrough |
P137177
|
FINISHED |
| Object | family gatherings |
—
|
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: family gatherings | Statement: [Umoja, isEncouragedThrough, family gatherings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEncouragedThrough Context triple: [Umoja, isEncouragedThrough, family gatherings]
-
A.
isEncouragedInContext
chosen
Indicates that an action, behavior, or state is positively promoted, supported, or recommended within a specific context or situation.
-
B.
settlementEncouragedBy
Indicates that the establishment or growth of a settlement is promoted, supported, or stimulated by a particular factor, agent, or condition.
-
C.
encourages
Indicates actively motivating, supporting, or giving confidence to another entity to pursue an action, behavior, or state.
-
D.
depictedAsEncouraging
Indicates that one entity is portrayed or represented as giving support, confidence, or motivation to another entity.
-
E.
providesIncentivesTo
Indicates that one entity offers rewards, benefits, or motivations to another entity to encourage a desired behavior or outcome.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.