Triple
T30496441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadariba |
E776018
|
entity |
| Predicate | associatedWithPastoralism |
P207278
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hadariba, associatedWithPastoralism, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPastoralism Context triple: [Hadariba, associatedWithPastoralism, true]
-
A.
usesPastoralSetting
Indicates that the action or work is set in an idealized rural or countryside environment characteristic of pastoral themes.
-
B.
pastoralActivities
Indicates activities related to providing spiritual care, guidance, or religious leadership within a community.
-
C.
hasPastoralArea
Indicates that one entity is assigned to, responsible for, or associated with a specific pastoral area or pastoral care region of another entity.
-
D.
pastoralGoal
Indicates that an entity has a religious or spiritual care objective directed toward another entity or group.
-
E.
pastoralPurpose
Indicates that something is intended or designated for pastoral use, care, or ministry within a religious or spiritual context.
- F. None of above. chosen
Provenance (4 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:14 p.m.