Triple
T7252838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Most Holy Place |
E157645
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | debir |
E515855
|
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: debir | Statement: [Most Holy Place, hasAlternativeName, debir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: debir Context triple: [Most Holy Place, hasAlternativeName, debir]
-
A.
DEB
DEB is the abbreviation for the Deutscher Eishockey-Bund, the governing body for ice hockey in Germany.
-
B.
De
De is the given name of Zhu De, a prominent Chinese Communist military leader and one of the founders of the People’s Liberation Army.
-
C.
Debub
Debub is a southern administrative region of Eritrea known for its highland landscapes, agriculture, and historical sites.
-
D.
Debir
chosen
Debir is an ancient Canaanite city mentioned in the Hebrew Bible, located in the hill country of Judah and associated with Israelite conquest narratives.
-
E.
beit din
A beit din is a Jewish rabbinical court that adjudicates matters of religious law, personal status, and communal disputes according to halakha.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea9d41908190bb76c6a5b9d5b1a2 |
completed | March 27, 2026, 8:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7d3ac0de88190990c1ef25636260c |
completed | March 28, 2026, 1:12 p.m. |
Created at: March 27, 2026, 2:56 p.m.