Triple
T14721277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillsborough Historic District |
E345819
|
entity |
| Predicate | hasTimePeriodRepresented |
P58089
|
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: [Hillsborough Historic District, hasTimePeriodRepresented, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimePeriodRepresented Context triple: [Hillsborough Historic District, hasTimePeriodRepresented, 18th century]
-
A.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
-
B.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
C.
hasHistoryPeriod
chosen
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
D.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
E.
hasCountingPeriod
Indicates that there is a defined time span or interval over which occurrences, quantities, or measurements related to an entity are counted or aggregated.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec25d56fc8190871873ca55d49272 |
completed | April 14, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.