Triple
T26567895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encratism |
E666740
|
entity |
| Predicate | regardsMarriageAs |
P161039
|
FINISHED |
| Object | sinful |
—
|
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: sinful | Statement: [Encratism, regardsMarriageAs, sinful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regardsMarriageAs Context triple: [Encratism, regardsMarriageAs, sinful]
-
A.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
B.
marriageResolvedBy
Indicates that a marital relationship between two parties has been formally concluded or dissolved through a specific resolving action or process (e.g., divorce, annulment).
-
C.
marriageContext
Indicates the situational or cultural circumstances under which a marriage occurs or exists, such as legal, social, or religious conditions surrounding the marital relationship.
-
D.
involvesMarriage
Indicates that the relationship or action includes or is characterized by a marriage between the involved entities.
-
E.
maritalBasis
Indicates that the relationship or status in question is founded on, justified by, or determined due to a marital relationship between the involved entities.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614a0c2408190b494a3d1f624c042 |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 1:56 a.m.