Triple
T14180171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebabbar |
E351430
|
entity |
| Predicate | widerCultNetwork |
P63283
|
FINISHED |
| Object | temples of Shamash in Mesopotamia |
—
|
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: temples of Shamash in Mesopotamia | Statement: [Ebabbar, widerCultNetwork, temples of Shamash in Mesopotamia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widerCultNetwork Context triple: [Ebabbar, widerCultNetwork, temples of Shamash in Mesopotamia]
-
A.
culturalInteraction
Indicates interactions or exchanges between entities that involve cultural practices, values, expressions, or influences.
-
B.
culturalSphere
Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by another entity.
-
C.
sharesCultWith
chosen
Indicates that two entities belong to or participate in the same cult or cult-like religious group.
-
D.
hasCulturalScope
Indicates that a relationship or action is limited to, relevant within, or characterized by a particular cultural context or domain.
-
E.
culturalExport
Indicates that something originating in one culture is transmitted, adopted, or influential in another culture or region.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61c90abc8190a9b9dc1f50db59fa |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:02 a.m.