Triple
T21649507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wars with Aram-Damascus |
E534298
|
entity |
| Predicate | hasLocation |
P40
|
FINISHED |
| Object | Aram |
—
|
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: Aram | Statement: [Wars with Aram-Damascus, hasLocation, Aram]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aram Context triple: [Wars with Aram-Damascus, hasLocation, Aram]
-
A.
Aram
Aram is a common Armenian given name with deep historical and cultural significance in Armenian heritage.
-
B.
Aram
Aram is the first book of the ancient Tamil text Tirukkural, focusing on virtue, ethics, and righteous living.
-
C.
Sahak
Sahak is an Armenian given name most famously borne by Sahak Partev, a prominent 5th-century Catholicos of the Armenian Apostolic Church and key figure in early Armenian Christianity.
-
D.
Aram-naharaim
chosen
Aram-naharaim is an ancient region in northern Mesopotamia, often identified with the area between the Tigris and Euphrates rivers and frequently mentioned in the Hebrew Bible.
-
E.
Aravir
Aravir is a little-known Dúnedain chieftain of the House of Isildur in J.R.R. Tolkien’s legendarium, appearing in the genealogies leading to Aragorn.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59131c88819082df8e5b87f5954b |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 16, 2026, 6:35 p.m.