Triple
T3104591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warrenton Historic District |
E64800
|
entity |
| Predicate | hasArchitecturePeriod |
P9594
|
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: [Warrenton Historic District, hasArchitecturePeriod, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchitecturePeriod Context triple: [Warrenton Historic District, hasArchitecturePeriod, 19th century]
-
A.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
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.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
D.
hasArchitecturalFeature
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
E.
architectureHistory
Indicates a historical or developmental relationship between an entity and its architectural evolution, style, or significant architectural events over time.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29a90e88190afb8a10291ef1946 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.