Triple
T2101489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New History |
E37101
|
entity |
| Predicate | stanceTowardChristianity |
P6264
|
FINISHED |
| Object | critical |
—
|
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: critical | Statement: [New History, stanceTowardChristianity, critical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceTowardChristianity Context triple: [New History, stanceTowardChristianity, critical]
-
A.
religiousReception
Indicates a relationship where one entity formally receives, welcomes, or hosts another in a specifically religious or faith-based context.
-
B.
hadViewOnReligion
chosen
Indicates that an entity held a particular perspective, belief, or stance regarding religion.
-
C.
statusInChristianity
Indicates the recognized role, standing, or significance that something or someone holds within Christian belief, practice, or tradition.
-
D.
portraysReligionAs
Indicates that one entity represents, depicts, or characterizes a religion in a particular way.
-
E.
bearerReligion
Indicates that a bearer (such as a person or entity) adheres to, practices, or is associated with a particular religion.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabc83a8819091f786f21d33b5a6 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.