Triple
T21217203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King’s Highway |
E522866
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Ammon |
—
|
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: Ammon | Statement: [King’s Highway, passesThrough, Ammon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ammon Context triple: [King’s Highway, passesThrough, Ammon]
-
A.
Ammon
chosen
Ammon was an ancient kingdom located east of the Jordan River, often interacting and clashing with the Israelites throughout biblical history.
-
B.
Amon
Amon was a king of Judah in the Hebrew Bible, known for continuing the idolatrous practices of his father Manasseh and being assassinated after a short reign.
-
C.
Amenth
Amenth is a hellish, demonic dimension in Marvel's X-Men comics, home to the monstrous forces that warred with the mutant nation of Arakko.
-
D.
Reuel
Reuel is a biblical figure identified as another name for Jethro, the Midianite priest and father-in-law of Moses.
-
E.
Reuel
Reuel is the middle name of famed English author and philologist J. R. R. Tolkien, used as part of his full name John Ronald Reuel Tolkien.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734744dcc81908b3065adc93b4b98 |
completed | April 21, 2026, 8:25 a.m. |
Created at: April 16, 2026, 3:41 p.m.