Triple
T3700815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Walker |
E78572
|
entity |
| Predicate | religiousHypocrisy |
P49475
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tom Walker, religiousHypocrisy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousHypocrisy Context triple: [Tom Walker, religiousHypocrisy, yes]
-
A.
religiousCritic
Indicates that one entity criticizes, challenges, or expresses disapproval of another entity on religious grounds or regarding religious beliefs, practices, or institutions.
-
B.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
C.
religiousAttitude
Indicates an entity’s stance, disposition, or orientation toward religion or religious beliefs.
-
D.
bearerReligion
Indicates that a bearer (such as a person or entity) adheres to, practices, or is associated with a particular religion.
-
E.
religiousConsequence
Indicates a relationship where one event, action, or state leads to an outcome specifically defined or understood in religious terms (such as divine reward, punishment, obligation, or spiritual effect).
- F. None of above. chosen
Provenance (4 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc514eb6c8190b3b74a603c717729 |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb903be308190a8f1925f99e67c68 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:26 p.m.