Triple
T10584884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwichtown Historic District |
E249828
|
entity |
| Predicate | hasPeakDevelopmentPeriod |
P24285
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Norwichtown Historic District, hasPeakDevelopmentPeriod, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakDevelopmentPeriod Context triple: [Norwichtown Historic District, hasPeakDevelopmentPeriod, 18th century]
-
A.
hadGrowthPeriod
chosen
Indicates that an entity experienced a specific span of time during which it underwent growth or development.
-
B.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
C.
developedOverPeriod
Indicates that something was created, expanded, or progressed continuously throughout a specified span of time.
-
D.
hasBuildingPeriod
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
-
E.
developsUntil
Indicates that a process, condition, or entity continues to develop or progress up to a specified point or limit in time or state.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52768da9c8190add1db88bf2e16ea |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:39 p.m.