Triple
T26704890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinka religion |
E673261
|
entity |
| Predicate | moralCodeBasedOn |
P27668
|
FINISHED |
| Object | kinship obligations |
—
|
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: kinship obligations | Statement: [Dinka religion, moralCodeBasedOn, kinship obligations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moralCodeBasedOn Context triple: [Dinka religion, moralCodeBasedOn, kinship obligations]
-
A.
hasMoralCode
Indicates that an entity adheres to or is guided by a set of moral principles or ethical rules.
-
B.
moralCriterion
Indicates that something is being evaluated or classified according to a standard of moral judgment or ethical rightness.
-
C.
derivesMoralityFrom
chosen
Indicates that one entity bases or grounds its moral principles, judgments, or ethical framework on another entity.
-
D.
moralBelief
Indicates that an agent holds a normative judgment about what is right, wrong, good, or bad in a given context.
-
E.
moralJustification
Indicates that an action, decision, or state is regarded as ethically right, acceptable, or defensible according to a moral standard.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 3:33 a.m.