Triple
T9661932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An |
E233609
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Antu |
E233602
|
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: Antu | Statement: [An, spouse, Antu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Antu Context triple: [An, spouse, Antu]
-
A.
Antu
Antu is one of the four 8.2-meter Unit Telescopes of the Very Large Telescope array operated by the European Southern Observatory at Paranal in Chile.
-
B.
Antu
chosen
Antu is a Mesopotamian sky and mother goddess, best known as the consort of the supreme god Anu in ancient Sumerian and Akkadian religion.
-
C.
Tanto
Tanto was a former town in Hyōgo Prefecture, Japan, that later became part of the expanded city of Toyooka through municipal merger.
-
D.
Machaon
Machaon is a figure from Greek mythology, renowned as a skilled healer and son of the legendary physician Asclepius.
-
E.
Entemena
Entemena was an early dynastic Sumerian ruler of the city-state of Lagash, known for consolidating its power and commissioning some of the earliest known royal inscriptions.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0b7728819099473f404382b26a |
completed | April 1, 2026, 10:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18a1422348190967943b0d4da8efd |
completed | April 4, 2026, 10 p.m. |
Created at: March 30, 2026, 8:14 p.m.