Triple
T22593943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clinton Avenue (Albany, New York) |
E574621
|
entity |
| Predicate | hasEraOfMostDevelopment |
P95
|
FINISHED |
| Object | 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: 19th century | Statement: [Clinton Avenue (Albany, New York), hasEraOfMostDevelopment, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEraOfMostDevelopment Context triple: [Clinton Avenue (Albany, New York), hasEraOfMostDevelopment, 19th century]
-
A.
hasEarliestUrbanDevelopment
Indicates that one location experienced the beginning of urban development earlier in time than another location.
-
B.
wasDevelopedInPeriod
chosen
Indicates that something was created, produced, or brought into existence during a specified time period.
-
C.
hasEraInfluence
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
-
D.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
-
E.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f16163cb248190b377b110d80a6730 |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:49 p.m.