Triple
T5373242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Othniel |
E108900
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Kenaz |
E515852
|
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: Kenaz | Statement: [Othniel, father, Kenaz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kenaz Context triple: [Othniel, father, Kenaz]
-
A.
Kenaz
chosen
Kenaz is a biblical family name associated with a clan in the tribe of Judah, notably linked to the judge Othniel.
-
B.
Kenberma
Kenberma is a coastal village neighborhood within the town of Hull, Massachusetts, known for its residential community and proximity to Nantasket Beach.
-
C.
Qadan
Qadan was a 13th-century Mongol military leader and prince of the Borjigin dynasty who led Mongol forces during their campaign in Poland.
-
D.
Zayanes
Zayanes are a Berber (Amazigh) ethnic group indigenous to Morocco’s Middle Atlas region, known for their distinct language, culture, and tribal history.
-
E.
Kandan
Kandan is a locality within Beijing’s Fengtai District, known primarily as a residential and urban neighborhood area.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd86abc1e88190ad08279c3bf238e5 |
completed | March 20, 2026, 5:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf334ac2548190ad672943ac138373 |
completed | March 22, 2026, 12:09 a.m. |
Created at: March 20, 2026, 2:03 p.m.