Triple
T6447679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baal Shem Tov |
E139782
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Adil |
E554544
|
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: Adil | Statement: [Baal Shem Tov, child, Adil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adil Context triple: [Baal Shem Tov, child, Adil]
-
A.
Adil
chosen
Adil is a common male given name of Arabic origin, meaning "just" or "fair."
-
B.
Fazl
Fazl is the given name of Fazl-e-Haq Khairabadi, a 19th-century Indian Islamic scholar, philosopher, and prominent figure in the Indian Rebellion of 1857.
-
C.
Jawad
Jawad is a masculine given name of Arabic origin commonly used across the Middle East and Muslim-majority regions.
-
D.
Abdul
Abdul is a common male given name of Arabic origin meaning "servant of" (typically followed by one of the names of God).
-
E.
Khair
Khair is a town in the Indian state of Uttar Pradesh, situated within the culturally significant Braj region associated with the legends of Lord Krishna.
- 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069afd8c48190b3cab580c813ecab |
completed | March 22, 2026, 10:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c64bcfc7388190877ad702ea44802d |
completed | March 27, 2026, 9:20 a.m. |
Created at: March 22, 2026, 4:47 p.m.