Triple
T29135352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mistress of Isheru |
E738498
|
entity |
| Predicate | cultCenterOfDeity |
P114792
|
FINISHED |
| Object | Mut |
—
|
NE NERFINISHED |
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: Mut | Statement: [Mistress of Isheru, cultCenterOfDeity, Mut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultCenterOfDeity Context triple: [Mistress of Isheru, cultCenterOfDeity, Mut]
-
A.
centralDeitySymbol
Indicates that one entity serves as the primary or central symbolic representation of a deity for another entity.
-
B.
mainDeityLocation
Indicates the place or setting where the primary deity associated with something is located or worshipped.
-
C.
centerOfCultFrom
chosen
Indicates that a location serves as the primary cult center or focal place of worship originating from a particular source or entity.
-
D.
centerOfCult
Indicates that the subject functions as the primary focus or core figure around which a cult is organized or devoted.
-
E.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6623013c88190a87411424f9af256 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:34 a.m.