Triple
T10724701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ur |
E252909
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Urim |
E592948
|
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: Urim | Statement: [Ur, alsoKnownAs, Urim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Urim Context triple: [Ur, alsoKnownAs, Urim]
-
A.
Urim
chosen
Urim is an ancient Israelite sacred object, traditionally paired with the Thummim, used by priests for divination and seeking God’s guidance.
-
B.
Neuli
Neuli is a small village located in the scenic Sainj Valley of Himachal Pradesh, India, known for its tranquil rural setting amid the Himalayas.
-
C.
Huram
Huram is an alternative biblical form of the name Hiram, commonly associated with figures linked to the construction of Solomon’s Temple.
-
D.
Zorah
Zorah was an ancient town in the territory of the Tribe of Dan, known from the Hebrew Bible as the hometown of Samson.
-
E.
Tirhuta
Tirhuta is a historical Brahmic script traditionally used for writing the Maithili language in the Mithila region of India and Nepal.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70d473cfc8190b0ea6dbec14ee070 |
completed | April 9, 2026, 2:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dbb741a174819098aafac90d29d50a |
completed | April 12, 2026, 3:16 p.m. |
Created at: April 8, 2026, 9:14 p.m.