Triple
T9040279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Ground |
E216605
|
entity |
| Predicate | hasReligiousThemes |
P24743
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rocky Ground, hasReligiousThemes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousThemes Context triple: [Rocky Ground, hasReligiousThemes, true]
-
A.
hasReligiousTheme
chosen
Indicates that something (such as a work, event, or object) centrally involves or expresses religious ideas, symbols, practices, or narratives.
-
B.
hasReligiousSee
Indicates that one entity serves as the ecclesiastical or religious jurisdiction/seat (see) of another entity.
-
C.
hasReligiousForms
Indicates that an entity possesses or is associated with specific religious expressions, practices, or organizational structures.
-
D.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
E.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b100a348190a59abd6e9b815c63 |
completed | April 1, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.