Triple
T18451027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satya Yuga |
E450780
|
entity |
| Predicate | humanNature |
P80897
|
FINISHED |
| Object | innate goodness |
—
|
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: innate goodness | Statement: [Satya Yuga, humanNature, innate goodness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanNature Context triple: [Satya Yuga, humanNature, innate goodness]
-
A.
exploresHumanNature
Indicates a relationship in which a subject examines, analyzes, or reflects on fundamental aspects of human behavior, emotions, motivations, and identity.
-
B.
attitudeTowardHumanNature
chosen
Indicates an entity’s evaluative stance or belief about the fundamental characteristics and tendencies of human nature.
-
C.
hasNature
Indicates that something possesses, exhibits, or is characterized by a particular inherent quality, essence, or fundamental type.
-
D.
naturalOrHumanCause
Indicates that something results from either natural processes or human activities as its cause.
-
E.
digitalNature
Indicates a relationship where something exists, operates, or is characterized primarily in a digital or computational form rather than a physical or analog one.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52648476c8190a5d8c3297d836f62 |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.