Triple
T4604945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talbotton, Georgia |
E100408
|
entity |
| Predicate | architecturalEraNotable |
P561
|
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: [Talbotton, Georgia, architecturalEraNotable, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalEraNotable Context triple: [Talbotton, Georgia, architecturalEraNotable, 19th century]
-
A.
architecturalContribution
Indicates a relationship where an entity contributes to the design, planning, or creation of an architectural work or feature.
-
B.
architecturalInfluence
Indicates that one architectural style, structure, or designer has had a formative impact on the design, style, or features of another.
-
C.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
D.
architectureHistory
Indicates a historical or developmental relationship between an entity and its architectural evolution, style, or significant architectural events over time.
-
E.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5999f9c88190a43309573df61159 |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.