Triple
T13431295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Green |
E313615
|
entity |
| Predicate | hasReligionRelatedActivity |
P21643
|
FINISHED |
| Object | Bible collection |
—
|
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: Bible collection | Statement: [Steve Green, hasReligionRelatedActivity, Bible collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionRelatedActivity Context triple: [Steve Green, hasReligionRelatedActivity, Bible collection]
-
A.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
B.
religiousActivity
chosen
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
C.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
D.
hasReligiousMovement
Indicates that an entity is associated with, follows, or is characterized by a particular religious movement.
-
E.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed41a5481908800033303224adb |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.