Triple
T18223082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aram |
E436353
|
entity |
| Predicate | hasVariantForm |
P457
|
FINISHED |
| Object | Arame |
—
|
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: Arame | Statement: [Aram, hasVariantForm, Arame]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arame Context triple: [Aram, hasVariantForm, Arame]
-
A.
Arameans
chosen
The Arameans were an ancient Semitic people of the Near East who spoke Aramaic and established a number of small kingdoms in regions of modern-day Syria and Mesopotamia.
-
B.
Aram
Aram is the first book of the ancient Tamil text Tirukkural, focusing on virtue, ethics, and righteous living.
-
C.
Aram
Aram is a common Armenian given name with deep historical and cultural significance in Armenian heritage.
-
D.
Adiabene
Adiabene was an ancient kingdom in northern Mesopotamia, notable for its ruling dynasty’s conversion to Judaism and its role as a client state of the Parthian and later Roman Empires.
-
E.
Amurru
Amurru is an ancient Mesopotamian god associated with the Amorite people, often linked to the steppe, pastoralism, and sometimes storm or weather phenomena.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e47d9b348190897d5a1e70b39ec5 |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 10:32 a.m.