Triple
T9359795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Salem, Massachusetts |
E225248
|
entity |
| Predicate | charteredAsCity |
P306
|
FINISHED |
| Object | 1836 |
—
|
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: 1836 | Statement: [History of Salem, Massachusetts, charteredAsCity, 1836]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charteredAsCity Context triple: [History of Salem, Massachusetts, charteredAsCity, 1836]
-
A.
incorporatedAsCity
chosen
Indicates that an entity was formally established and legally recognized as a city.
-
B.
foundedAsMetropolis
Indicates that an entity was originally established or designated as a metropolis, typically a major or principal city.
-
C.
cityStatusGrantedIn
Indicates the event or point in time at which an entity was officially granted city status in a particular place or jurisdiction.
-
D.
cityStatusGrantedInMemoryOf
Indicates that city status was conferred on a place specifically to honor or commemorate a particular person, event, or entity.
-
E.
proclaimedCity
Indicates that an authority or source has officially announced or declared a particular city in relation to something (such as a title, status, or event).
- 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_69ca842bdd648190904131d58620d448 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4ff2ca9081908ccc88651640ed84 |
completed | April 1, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:42 p.m.