Triple
T8092359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbour County |
E188896
|
entity |
| Predicate | hasHistoricArchitectureType |
P6684
|
FINISHED |
| Object | antebellum homes |
—
|
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: antebellum homes | Statement: [Barbour County, hasHistoricArchitectureType, antebellum homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricArchitectureType Context triple: [Barbour County, hasHistoricArchitectureType, antebellum homes]
-
A.
hasArchitecturalSignificance
Indicates that something possesses notable architectural qualities, importance, or influence that make it worthy of special attention or recognition.
-
B.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
C.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
D.
architectureHistory
Indicates a historical or developmental relationship between an entity and its architectural evolution, style, or significant architectural events over time.
-
E.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
- 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42217a1881909792b08a2f06fb75 |
completed | March 31, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:30 p.m.