Triple
T1174556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springfield Downtown Historic District |
E24989
|
entity |
| Predicate | reflectsPeriod |
P4343
|
FINISHED |
| Object | late 19th 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: late 19th century | Statement: [Springfield Downtown Historic District, reflectsPeriod, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsPeriod Context triple: [Springfield Downtown Historic District, reflectsPeriod, late 19th century]
-
A.
refersToPeriod
chosen
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
B.
tienePeriodicidad
Indicates that something occurs, recurs, or is scheduled with a specific regular frequency or periodic pattern.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
E.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5844348190b01ac6506906ba3b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.