Triple
T7557609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gallows Hill |
E178708
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object | Salem |
E506983
|
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: Salem | Statement: [Gallows Hill, hasMunicipality, Salem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Salem Context triple: [Gallows Hill, hasMunicipality, Salem]
-
A.
Salem
Salem is a major city in the Indian state of Tamil Nadu, historically significant as an important administrative and commercial center under British rule.
-
B.
Salem
Salem is a supernatural horror television series that reimagines the infamous Salem witch trials with a dark, fictionalized narrative.
-
C.
Salem
chosen
Salem is a historic coastal city in Massachusetts best known for the 1692 witch trials and its well-preserved colonial architecture.
-
D.
Salem
Salem is an ancient biblical city traditionally associated with Jerusalem and referenced in the Hebrew Scriptures as a place of divine presence and peace.
-
E.
Salem
Salem was the original name of the small town now known as Marshall in Fauquier County, Virginia.
- 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8db3d508190850ed41854d69838 |
completed | March 27, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c870780d24819095196cd3a22bec5a |
completed | March 29, 2026, 12:21 a.m. |
Created at: March 27, 2026, 3:50 p.m.