Triple
T6707545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptah-Sokar-Osiris |
E153045
|
entity |
| Predicate | hasComponentDeity |
P45989
|
FINISHED |
| Object | Sokar |
E161828
|
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: Sokar | Statement: [Ptah-Sokar-Osiris, hasComponentDeity, Sokar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sokar Context triple: [Ptah-Sokar-Osiris, hasComponentDeity, Sokar]
-
A.
Sokar
chosen
Sokar is an ancient Egyptian funerary god associated with the Memphite necropolis, the afterlife, and aspects of death and rebirth.
-
B.
Sakaar
Sakaar is a chaotic, trash-covered planet ruled by the Grandmaster in the Marvel Cinematic Universe, known for its gladiatorial contests and bizarre cosmic detritus.
-
C.
Samalkha
Samalkha is a town in the northern Indian state of Haryana, known for its industrial activity and location along major transport routes.
-
D.
Akrar
Akrar is a small village located on the island of Suðuroy in the Faroe Islands.
-
E.
Hekari
Hekari is a regional dialect of the Kurmanji variety of the Kurdish language, spoken in parts of the Hakkari region.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1033bb881908c3360b715bf13cf |
completed | March 27, 2026, 6:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70af6d1608190887c5d9f94ffe9fa |
completed | March 27, 2026, 10:55 p.m. |
Created at: March 27, 2026, 2:06 p.m.