Triple
T5700542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vartoosh Adoian |
E125647
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Adoian |
E124308
|
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: Adoian | Statement: [Vartoosh Adoian, familyName, Adoian]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adoian Context triple: [Vartoosh Adoian, familyName, Adoian]
-
A.
Adoian
chosen
Adoian is the original Armenian surname of the influential abstract expressionist painter Arshile Gorky.
-
B.
Arkin
Arkin is a surname most notably associated with the late American actor and filmmaker Alan Arkin.
-
C.
Adi Keyh
Adi Keyh is a town in southern Eritrea known as a regional center near the ancient archaeological site of Qohaito.
-
D.
Adi
Adi is a given name most notably borne by Adi Shamir, an Israeli cryptographer and co-inventor of the RSA encryption algorithm.
-
E.
Adi
Adi are an indigenous tribal community of northeastern India, primarily inhabiting the hilly regions of Arunachal Pradesh and known for their distinct language, festivals, and agrarian lifestyle.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c024540afc8190aee3760f71ea39c2 |
completed | March 22, 2026, 5:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c05a5fe4fc8190944a63a29da0fe3c |
completed | March 22, 2026, 9:08 p.m. |
Created at: March 22, 2026, 3:45 p.m.