Triple
T14317642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U Street Historic District |
E354998
|
entity |
| Predicate | culturalPeakPeriod |
P9594
|
FINISHED |
| Object | early 20th 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: early 20th century | Statement: [U Street Historic District, culturalPeakPeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalPeakPeriod Context triple: [U Street Historic District, culturalPeakPeriod, early 20th century]
-
A.
culturalPeak
Indicates that an entity represents the highest or most flourishing point of its cultural development, influence, or achievement.
-
B.
culturalPeriod
chosen
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
C.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
D.
popularTimeToVisit
Indicates the time period during which a place is most frequently visited or experiences peak visitor activity.
-
E.
popularInPeriod
Indicates that something is widely liked, used, or influential during a specified 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883a93548190ac671b001d15d0bd |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.