Triple
T25615889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Washington Butler |
E642158
|
entity |
| Predicate | religiousOrIdeologicalPosition |
P36791
|
FINISHED |
| Object | anti-evolutionism |
—
|
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: anti-evolutionism | Statement: [John Washington Butler, religiousOrIdeologicalPosition, anti-evolutionism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousOrIdeologicalPosition Context triple: [John Washington Butler, religiousOrIdeologicalPosition, anti-evolutionism]
-
A.
positionInReligion
Indicates the specific role, rank, or office an entity holds within a religious organization or tradition.
-
B.
religiousAttitude
chosen
Indicates an entity’s stance, disposition, or orientation toward religion or religious beliefs.
-
C.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
-
D.
religiousOrientationRole
Indicates a role or position that an entity holds in relation to a particular religious orientation or affiliation.
-
E.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 21, 2026, 5 p.m.