Triple
T5672987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Ladies |
E125020
|
entity |
| Predicate | refersTo |
P37
|
FINISHED |
| Object | Wadjet |
E24038
|
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: Wadjet | Statement: [Two Ladies, refersTo, Wadjet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wadjet Context triple: [Two Ladies, refersTo, Wadjet]
-
A.
Wadjet
chosen
Wadjet is an ancient Egyptian cobra goddess associated with royal protection, kingship, and the land of Lower Egypt.
-
B.
Nekhbet
Nekhbet is an ancient Egyptian vulture goddess who served as the protective patron deity of Upper Egypt and the pharaoh.
-
C.
Taweret
Taweret is an ancient Egyptian protective goddess, typically depicted as a pregnant hippopotamus, who guarded childbirth and mothers.
-
D.
Swenet
Swenet is the ancient Egyptian city known to the Greeks as Syene, located at modern-day Aswan near Egypt’s southern frontier.
-
E.
Wepwawet
Wepwawet is an ancient Egyptian jackal-headed war and funerary god, often depicted as a path-opener who guided kings and the dead.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0236e8dc48190b4eb7709a258909f |
completed | March 22, 2026, 5:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1133b6ce0819080ec5d6bad6d2e97 |
completed | March 23, 2026, 10:17 a.m. |
Created at: March 22, 2026, 3:43 p.m.