Triple
T9817709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Story |
E238449
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Salem, Massachusetts |
E23727
|
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, Massachusetts | Statement: [Joseph Story, residence, Salem, Massachusetts]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Salem, Massachusetts Context triple: [Joseph Story, residence, Salem, Massachusetts]
-
A.
Salem, Massachusetts
chosen
Salem, Massachusetts is a historic coastal city in northeastern Massachusetts best known for the 1692 witch trials and its enduring maritime and colonial heritage.
-
B.
Salem
Salem is a mid-sized city in the Willamette Valley of the U.S. Pacific Northwest known for its government institutions and agricultural surroundings.
-
C.
Salem
Salem is a supernatural horror television series that reimagines the infamous Salem witch trials with a dark, fictionalized narrative.
-
D.
Salem
Salem is a small city in Utah County, Utah, known for its scenic pond, suburban character, and location within the Provo–Orem metropolitan area.
-
E.
Salem
Salem is a common Arabic male given name meaning "safe" or "peaceful," widely used across the Arab world.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f5bfa481908a2d2cb3f3d7d585 |
completed | April 2, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d20d2cb5108190aa15b60ea76bfa78 |
completed | April 5, 2026, 7:20 a.m. |
Created at: March 30, 2026, 8:30 p.m.