Triple
T644654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandwich Historic District |
E11213
|
entity |
| Predicate | eraOfInitialDevelopment |
P11886
|
FINISHED |
| Object | mid-17th century |
—
|
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: mid-17th century | Statement: [Sandwich Historic District, eraOfInitialDevelopment, mid-17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfInitialDevelopment Context triple: [Sandwich Historic District, eraOfInitialDevelopment, mid-17th century]
-
A.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
B.
developmentalFor
Indicates that one entity serves as a developmental precursor, stage, or necessary condition for the emergence or maturation of another entity.
-
C.
earliestStage
Indicates that one entity represents the first or minimum stage, phase, or step in a defined ordered sequence relative to another.
-
D.
developmentStart
chosen
Indicates the point in time or event when the development process of something begins.
-
E.
developedRapidlyDuring
Indicates that one entity experienced swift or accelerated development within the time period or context defined by another entity.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f19f9a08190b0bf6e19b32427ff |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0a0ab481909871461418a00be7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.