Triple
T19076264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manoah |
E466911
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Zorah |
—
|
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: Zorah | Statement: [Manoah, residence, Zorah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zorah Context triple: [Manoah, residence, Zorah]
-
A.
Zorah
chosen
Zorah was an ancient town in the territory of the Tribe of Dan, known from the Hebrew Bible as the hometown of Samson.
-
B.
Beth-zur
Beth-zur was an ancient fortified town in the Judean hill country, strategically important in the Maccabean period and frequently contested in Hellenistic-era conflicts.
-
C.
Elishama
Elishama is a biblical figure mentioned in the Old Testament, known primarily as one of King David’s sons.
-
D.
Voreqe
Voreqe is the Fijian given name of Frank Bainimarama, the former military commander and long-serving prime minister of Fiji.
-
E.
Urim
Urim is an ancient Israelite sacred object, traditionally paired with the Thummim, used by priests for divination and seeking God’s guidance.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e49c7c8190b6ce7b918086b23c |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 10, 2026, 12:04 p.m.