Triple
T1487076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bubastis |
E29489
|
entity |
| Predicate | greekName |
P3659
|
FINISHED |
| Object | Boubastis |
E29489
|
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: Boubastis | Statement: [Bubastis, greekName, Boubastis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Boubastis Context triple: [Bubastis, greekName, Boubastis]
-
A.
Nekhbet
Nekhbet is an ancient Egyptian vulture goddess who served as the protective patron deity of Upper Egypt and the pharaoh.
-
B.
Bubastis
chosen
Bubastis was an ancient Egyptian city in the Nile Delta best known as a major cult center of the cat goddess Bastet.
-
C.
Sobek
Sobek is an ancient Egyptian crocodile-headed god associated with the Nile, military power, and protection.
-
D.
Wadjet
Wadjet is an ancient Egyptian cobra goddess associated with royal protection, kingship, and the land of Lower Egypt.
-
E.
Sekhmet
Sekhmet is an ancient Egyptian lioness-headed goddess associated with war, destruction, and healing, revered as a powerful protector and bringer of both plague and cure.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a3325881909bbc55efc04ad60f |
completed | March 1, 2026, 11:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad7195dd10819096de0cde5fad5912 |
completed | March 8, 2026, 12:54 p.m. |
Created at: March 1, 2026, 8:12 p.m.