Triple
T19141778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadab |
E468575
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Baasha |
—
|
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: Baasha | Statement: [Nadab, associatedWith, Baasha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baasha Context triple: [Nadab, associatedWith, Baasha]
-
A.
Baasha
chosen
Baasha was a king of the northern Kingdom of Israel in the Hebrew Bible, known for overthrowing the previous dynasty and establishing his own short-lived royal line.
-
B.
Bisha
Bisha is a major inland city in southwestern Saudi Arabia known for its agricultural production and strategic location within the Asir region.
-
C.
Bhalesi
Bhalesi is a regional dialect of the Western Pahari language spoken in parts of the western Himalayan region of India.
-
D.
Bosha
Bosha is an alternative name for the Lom people, a Romani-related ethnic group primarily found in the Caucasus region.
-
E.
Barshaini
Barshaini is a small Himalayan village in Himachal Pradesh, India, that serves as a popular base and trailhead for treks into the Parvati Valley and surrounding high-altitude landscapes.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e975e09c8190911e98e6e558615d |
completed | April 20, 2026, 8:53 a.m. |
Created at: April 10, 2026, 12:05 p.m.