Triple
T19851940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Micah |
E477016
|
entity |
| Predicate | hasCultObjects |
P124358
|
FINISHED |
| Object | ephod |
—
|
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: ephod | Statement: [House of Micah, hasCultObjects, ephod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCultObjects Context triple: [House of Micah, hasCultObjects, ephod]
-
A.
hasCultSince
Indicates that an entity has had an organized group of devoted followers (a cult) continuously since a specified time or date.
-
B.
hasCultFeature
Indicates that an entity possesses a characteristic, attribute, or element associated with cultic or ritual practices.
-
C.
hasAttestedCult
Indicates that an entity is known to have had an established, historically attested cult or formal worship practice.
-
D.
associatedWithCultObject
chosen
Indicates that an entity has a relationship or connection to a cult object, such as being used for, dedicated to, or symbolically linked with it.
-
E.
typeOfCultObject
Indicates that one entity is the specific kind or category of cult object to which the other entity belongs or is classified.
- 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.