Triple
T49173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salem Village |
E966
|
entity |
| Predicate | siteOf |
P1205
|
FINISHED |
| Object | initial accusations in the Salem witch trials |
—
|
LITERAL 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: initial accusations in the Salem witch trials | Statement: [Salem Village, siteOf, initial accusations in the Salem witch trials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteOf Context triple: [Salem Village, siteOf, initial accusations in the Salem witch trials]
-
A.
site
chosen
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
-
B.
foundationPlace
Indicates the place where an organization, institution, or similar entity was originally founded or established.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
E.
mouthOf
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
- F. None of above.
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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abfa7bc8190932c137a823efcb6 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.