Triple
T9661891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adad |
E233608
|
entity |
| Predicate | associatedDeity |
P1481
|
FINISHED |
| Object | Shala |
E813884
|
NE 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: Shala | Statement: [Adad, associatedDeity, Shala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shala Context triple: [Adad, associatedDeity, Shala]
-
A.
Shala
chosen
Shala is a Mesopotamian goddess associated with weather and grain, best known as the wife of the storm god Adad (Ishkur).
-
B.
Sharya
Sharya is a town in Kostroma Oblast, Russia, known as a regional railway junction and logging center.
-
C.
Shara
Shara is an ancient Mesopotamian deity, primarily known as the warrior god and tutelary divine figure associated with the city-state of Umma in Sumer.
-
D.
Salala
Salala is a town in central Liberia that serves as an important local hub within Bong County.
-
E.
Salora
Salora was a prominent Finnish electronics manufacturer best known for producing televisions and radios, and it played a key role in the industrial history of Salo, Finland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0b7728819099473f404382b26a |
completed | April 1, 2026, 10:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d190f26df0819085d6f8b6228062bd |
completed | April 4, 2026, 10:30 p.m. |
Created at: March 30, 2026, 8:14 p.m.