Triple
T18893332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assem Allam |
E462147
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Allam |
—
|
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: Allam | Statement: [Assem Allam, familyName, Allam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Allam Context triple: [Assem Allam, familyName, Allam]
-
A.
Allam
chosen
Allam is a surname of Arabic origin borne by various notable individuals across fields such as acting, politics, and academia.
-
B.
Alladi
Alladi is an Indian surname notably associated with the distinguished jurist and constitutional expert Alladi Krishnaswamy Iyer.
-
C.
Alimin
Alimin was an early 20th-century Indonesian communist leader and activist who played a key role in the formation of the country’s communist movement.
-
D.
Asalluhi
Asalluhi is a Mesopotamian god associated with incantations, healing, and exorcism, often linked to the later Babylonian deity Marduk.
-
E.
Amlash
Amlash is a city in northern Iran known for its location in the lush, Caspian coastal region of Gilan Province.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c47d392c81909297211c7d7610a1 |
completed | April 20, 2026, 6:15 a.m. |
Created at: April 10, 2026, 11:58 a.m.