Triple
T11407560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Prohibition |
E270276
|
entity |
| Predicate | hasMainMessage |
P85911
|
FINISHED |
| Object | upholding divine limits in personal and family life |
—
|
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: upholding divine limits in personal and family life | Statement: [The Prohibition, hasMainMessage, upholding divine limits in personal and family life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainMessage Context triple: [The Prohibition, hasMainMessage, upholding divine limits in personal and family life]
-
A.
hasMainBody
Indicates that one entity serves as the primary physical or structural body of another entity.
-
B.
hasKeyMessage
chosen
Indicates that one entity conveys, contains, or is associated with a primary or central message of another entity.
-
C.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
D.
hasMainSource
Indicates that one entity serves as the primary or principal source or origin for another entity.
-
E.
hasMessageNumber
Indicates that an entity is associated with a specific message identified by a particular number in a sequence or set.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014e72748190a01bde2f0105cedb |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.