Triple
T30164081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enki in Eridu |
E766747
|
entity |
| Predicate | hasMainCultCenter |
P103522
|
FINISHED |
| Object | Eridu |
—
|
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: Eridu | Statement: [Enki in Eridu, hasMainCultCenter, Eridu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCultCenter Context triple: [Enki in Eridu, hasMainCultCenter, Eridu]
-
A.
hasMainCult
chosen
Indicates that an entity is associated with a primary or predominant cult or religious worship tradition.
-
B.
hasImperialCultCenter
Indicates that a place serves or served as a center for the worship and official cult of an emperor or imperial authority.
-
C.
hasNoMajorCultCenters
Indicates that the associated entity lacks any significant or widely recognized primary places of worship or veneration.
-
D.
hasMajorHistoricalCentersIn
Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
-
E.
centerOfCultFrom
Indicates that a location serves as the primary cult center or focal place of worship originating from a particular source or entity.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff8cecbf048190860b9f72b8753f5c |
completed | May 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69ff8c4c39dc8190b5bf35adc1bae7c6 |
completed | May 9, 2026, 7:34 p.m. |
Created at: April 29, 2026, 7:22 p.m.