Triple
T18484384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ankhesenamun |
E451647
|
entity |
| Predicate | relative |
P37
|
FINISHED |
| Object | Ay |
—
|
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: Ay | Statement: [Ankhesenamun, relative, Ay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ay Context triple: [Ankhesenamun, relative, Ay]
-
A.
Ay
chosen
Ay was a short-reigning ancient Egyptian pharaoh of the late 18th Dynasty, known for succeeding Tutankhamun and ruling during the turbulent period following the Amarna era.
-
B.
Ay
Ay is a historic French town in the Marne department renowned for its prestigious Champagne houses and vineyards.
-
C.
AY
AY is the IATA airline designator assigned to Finnair, the flag carrier and largest airline of Finland.
-
D.
AY
AY is the commonly used abbreviation for Alliance Youth, a Christian youth ministry associated with the Christian and Missionary Alliance.
-
E.
Ayy
Ayy is a town in Jordan’s Karak region known for its historical significance and proximity to the ancient Crusader stronghold of Karak.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d6502c8190af167b954bf8e989 |
completed | April 19, 2026, 7:49 p.m. |
Created at: April 10, 2026, 11:35 a.m.