Triple
T33879002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliza Reed |
E868432
|
entity |
| Predicate | religiousDisposition |
P36791
|
FINISHED |
| Object | strictly religious |
—
|
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: strictly religious | Statement: [Eliza Reed, religiousDisposition, strictly religious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousDisposition Context triple: [Eliza Reed, religiousDisposition, strictly religious]
-
A.
religiousAttitude
chosen
Indicates an entity’s stance, disposition, or orientation toward religion or religious beliefs.
-
B.
religiousMood
Indicates a prevailing emotional or spiritual atmosphere associated with religious experience, practice, or devotion between entities.
-
C.
religiousSide
Indicates that one entity is aligned with, belongs to, or represents a particular religious faction, denomination, or side in a religious context.
-
D.
positionInReligion
Indicates the specific role, rank, or office an entity holds within a religious organization or tradition.
-
E.
religiousMotivation
Indicates that an action, decision, or relationship is driven or significantly influenced by religious beliefs, values, or obligations.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 1, 2026, 1:48 a.m.