Triple
T18207257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Marriage of Heaven and Hell |
E435938
|
entity |
| Predicate | questionsConcept |
P71095
|
FINISHED |
| Object | conventional morality |
—
|
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: conventional morality | Statement: [The Marriage of Heaven and Hell, questionsConcept, conventional morality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questionsConcept Context triple: [The Marriage of Heaven and Hell, questionsConcept, conventional morality]
-
A.
questionType
Indicates the specific category or kind of question that an item, query, or prompt belongs to.
-
B.
questionConveyedBy
Indicates that a particular question is expressed, communicated, or represented by a given medium, message, or artifact.
-
C.
questionTopic
chosen
Indicates that a question is about, concerns, or is primarily focused on a particular topic or subject.
-
D.
questionFormulation
Indicates that one entity formulates, poses, or expresses a question directed toward another entity or context.
-
E.
questionStructure
Indicates the structural or grammatical arrangement that defines how a question is formed or organized.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e2243de081908a5bcc7e2072eae7 |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.