Triple
T9359835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Salem, Massachusetts |
E225248
|
entity |
| Predicate | HouseOfSevenGablesStatus |
P88137
|
FINISHED |
| Object | historic site and museum in Salem |
—
|
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: historic site and museum in Salem | Statement: [History of Salem, Massachusetts, HouseOfSevenGablesStatus, historic site and museum in Salem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HouseOfSevenGablesStatus Context triple: [History of Salem, Massachusetts, HouseOfSevenGablesStatus, historic site and museum in Salem]
-
A.
house1
Indicates that something is identified or classified as a house or dwelling.
-
B.
houseFounded
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
-
C.
houseName
Indicates the specific name or designation assigned to a house.
-
D.
houseVisited
Indicates that a particular house has been visited by a specified entity or at a specified time.
-
E.
house2
Indicates a relationship where one entity is a secondary, related, or alternative house associated with another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:42 p.m.