Triple
T9157175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | theological liberalism |
E219734
|
entity |
| Predicate | oftenQuestions |
P13891
|
FINISHED |
| Object | literal interpretation of miracles |
—
|
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: literal interpretation of miracles | Statement: [theological liberalism, oftenQuestions, literal interpretation of miracles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenQuestions Context triple: [theological liberalism, oftenQuestions, literal interpretation of miracles]
-
A.
questionText
Indicates the textual content of a question as it is posed or displayed.
-
B.
openingQuestion
Indicates that one entity poses an initial or introductory question to another, typically at the start of an interaction or dialogue.
-
C.
questionAsksWhether
Indicates that one entity poses a question to determine if a particular condition, fact, or proposition is true or not.
-
D.
questionConveyedBy
Indicates that a particular question is expressed, communicated, or represented by a given medium, message, or artifact.
-
E.
raisesQuestion
chosen
Indicates that one entity causes or prompts a question or doubt to arise about another entity or topic.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca9d6b9ac819094efe12c1ed67ecf |
completed | April 1, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:21 p.m.