Triple
T21606282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tꜣ-šmꜥ |
E533180
|
entity |
| Predicate | contrastedWith |
P278
|
FINISHED |
| Object | Ta-Mehu |
—
|
NE NERFINISHED |
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: Ta-Mehu | Statement: [tꜣ-šmꜥ, contrastedWith, Ta-Mehu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ta-Mehu Context triple: [tꜣ-šmꜥ, contrastedWith, Ta-Mehu]
-
A.
Ta-Mehu
chosen
Ta-Mehu is the ancient Egyptian name for Lower Egypt, the northern region of the Nile Valley encompassing the Nile Delta.
-
B.
Tamahú
Tamahú is a municipality and town located in the Alta Verapaz Department of central Guatemala, known for its highland landscapes and predominantly indigenous Maya population.
-
C.
Tauhunu
Tauhunu is a principal village and administrative center located on the atoll of Manihiki in the Cook Islands.
-
D.
The Turim
The Turim is a foundational 14th-century Jewish legal code by Rabbi Jacob ben Asher that systematically organizes halakhic rulings into four major sections.
-
E.
Tamachek
Tamachek is an alternative name for Tamasheq, a Berber language spoken by the Tuareg people of the Sahara region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e5783481909db36c388f3ae227 |
completed | April 27, 2026, 8:01 a.m. |
Created at: April 16, 2026, 6:33 p.m.