Triple
T370182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Avenue Historic Commercial District |
E8250
|
entity |
| Predicate | eraOfDevelopment |
P200
|
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: [Union Avenue Historic Commercial District, eraOfDevelopment, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfDevelopment Context triple: [Union Avenue Historic Commercial District, eraOfDevelopment, late 19th century]
-
A.
lifeStage
Indicates the specific phase or period in an entity’s development or lifecycle that it is currently in.
-
B.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
C.
eraOfSignificance
Indicates the historical period or timeframe during which an entity was particularly important, influential, or noteworthy.
-
D.
era
chosen
Indicates that something existed, occurred, or was valid during a specified historical or temporal period.
-
E.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebff472881909fad81d597425ea6 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e960d880819084b3df4e5137a1e2 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.