Triple
T4956600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherborn, Massachusetts |
E111294
|
entity |
| Predicate | hasPropertyTaxBase |
P59668
|
FINISHED |
| Object | primarily residential |
—
|
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: primarily residential | Statement: [Sherborn, Massachusetts, hasPropertyTaxBase, primarily residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropertyTaxBase Context triple: [Sherborn, Massachusetts, hasPropertyTaxBase, primarily residential]
-
A.
hasBaseArea
Indicates that one entity has a base whose surface area is quantified or associated with another entity.
-
B.
hasOwnTaxSystem
Indicates that an entity maintains and administers its own distinct system of taxation, separate from other jurisdictions or authorities.
-
C.
hasBasement
Indicates that a building or structure includes a basement level as part of its physical layout.
-
D.
hasEstateType
Indicates that an entity possesses or is associated with a particular category or type of estate.
-
E.
isTaxable
Indicates that the subject is legally subject to taxation under the applicable tax rules or regulations.
- 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.