Triple
T9180399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grafton, Massachusetts |
E220308
|
entity |
| Predicate | isHistoricNewEnglandTown |
P45268
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Grafton, Massachusetts, isHistoricNewEnglandTown, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricNewEnglandTown Context triple: [Grafton, Massachusetts, isHistoricNewEnglandTown, true]
-
A.
containsHistoricTown
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
B.
hasNewEnglandTownForm
Indicates that an entity possesses the characteristic municipal structure or governance pattern associated with a traditional New England town.
-
C.
isNewEnglandTown
chosen
Indicates that the subject is a town located within the New England region.
-
D.
hasMarketTownHistory
Indicates that an entity has a historical association with functioning as a market town or possessing recognized market-town status in the past.
-
E.
historicallyBasedIn
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc251da448190a5c7f684dac15a84 |
completed | April 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.