Triple
T11241982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terah |
E266092
|
entity |
| Predicate | diedIn |
P21
|
FINISHED |
| Object | Haran (city) |
E52250
|
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: Haran (city) | Statement: [Terah, diedIn, Haran (city)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haran (city) Context triple: [Terah, diedIn, Haran (city)]
-
A.
Haran
chosen
Haran is an ancient city in northern Mesopotamia known from the Hebrew Bible as a key dwelling place of the patriarch Abraham before his journey to Canaan.
-
B.
Haran
Haran is a biblical figure mentioned in the Book of Genesis, known as a member of Abraham’s extended family in the patriarchal narratives.
-
C.
Hapur
Hapur is a city in the Indian state of Uttar Pradesh, known as an industrial and grain market hub within the Delhi metropolitan area.
-
D.
Kfarhazir
Kfarhazir is a village in northern Lebanon known for its scenic hilltop location and traditional Lebanese rural character.
-
E.
Kfarhata
Kfarhata is a village located in the Koura District of northern Lebanon, known for its agricultural character and traditional rural setting.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e919eaf48190a1457851cfc56afb |
completed | April 9, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e509f7d404819086cf5d062edbaff5 |
completed | April 19, 2026, 4:59 p.m. |
Created at: April 8, 2026, 9:30 p.m.