Triple
T19268418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Seward |
E481850
|
entity |
| Predicate | worldviewChallengedBy |
P3648
|
FINISHED |
| Object | supernatural events |
—
|
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: supernatural events | Statement: [Jack Seward, worldviewChallengedBy, supernatural events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldviewChallengedBy Context triple: [Jack Seward, worldviewChallengedBy, supernatural events]
-
A.
worldview
Indicates the overarching perspective or framework through which an entity interprets and understands the world and its experiences.
-
B.
viewOfUnbelief
Indicates a perspective, attitude, or interpretation that is characterized by disbelief or lack of faith toward something.
-
C.
challengedConcept
chosen
Indicates that one entity has questioned, disputed, or called into doubt the validity, accuracy, or applicability of a particular concept.
-
D.
viewOfGod
Indicates a relationship where an entity holds a particular conception, perspective, or understanding of God.
-
E.
viewOnGod
Indicates a relationship where one entity holds or expresses a particular opinion, belief, or perspective about God.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb68d0c819083ba0ce680dd7d99 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.