Triple
T4956603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherborn, Massachusetts |
E111294
|
entity |
| Predicate | hasLocalHistoricCommission |
P59669
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sherborn, Massachusetts, hasLocalHistoricCommission, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalHistoricCommission Context triple: [Sherborn, Massachusetts, hasLocalHistoricCommission, yes]
-
A.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
B.
hasHistoricCommunity
Indicates that an entity is associated with, contains, or is part of a community of historical significance.
-
C.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
-
D.
hasHistoricMarker
Indicates that something is associated with or identified by an official historic marker or plaque recognizing its historical significance.
-
E.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71d6ba9c8190932f8d81240c3f56 |
completed | March 20, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3beb008190852fd6150813b252 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6d98dc88819083459a01d3e8fc45 |
completed | March 20, 2026, 3:54 p.m. |
Created at: March 20, 2026, 1:32 p.m.