Triple
T3154385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Mine |
E65948
|
entity |
| Predicate | containsReligiousReferences |
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: [All Mine, containsReligiousReferences, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsReligiousReferences Context triple: [All Mine, containsReligiousReferences, 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.
usedInReligiousTextsOf
Indicates that something (such as a concept, term, or symbol) appears within and is employed in the religious texts associated with a particular religion or tradition.
-
C.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
D.
associatedReligionInTexts
Indicates that a particular religion is mentioned or linked in written texts in connection with the given entity.
-
E.
hasReligiousOrigin
Indicates that something originates from, is derived from, or is fundamentally based on a religious tradition, belief system, or 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5e7f4688190b477186254f8a572 |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.