Triple
T19851957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Micah |
E477016
|
entity |
| Predicate | worshipCharacterizedAs |
P11149
|
FINISHED |
| Object | syncretistic |
—
|
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: syncretistic | Statement: [House of Micah, worshipCharacterizedAs, syncretistic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipCharacterizedAs Context triple: [House of Micah, worshipCharacterizedAs, syncretistic]
-
A.
worshipperType
Indicates the specific category or kind of worshipper involved in a religious or devotional relationship or action.
-
B.
worshipType
chosen
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
C.
worshipSymbol
Indicates a relationship where one entity venerates, honors, or directs religious devotion toward another entity as a sacred symbol.
-
D.
worshipLinkedTo
Indicates that an act or practice of worship is connected or associated with a particular entity, concept, or context.
-
E.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65869e1b481908e2a2a2074ff4a6d |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.