Triple
T24059333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Hill, Maryland |
E595897
|
entity |
| Predicate | hasHistoricBuildingsFromCentury |
P93743
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Church Hill, Maryland, hasHistoricBuildingsFromCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricBuildingsFromCentury Context triple: [Church Hill, Maryland, hasHistoricBuildingsFromCentury, 18th century]
-
A.
containsBuildingFromCentury
chosen
Indicates that a location or area includes at least one building that originates from a specified century.
-
B.
hasCenturyOldArchitecture
Indicates that something features architecture that is at least one hundred years old.
-
C.
constructionCentury
Indicates the century during which something was constructed or built.
-
D.
hasHistoricChurches
Indicates that an entity possesses or contains one or more churches of recognized historical significance.
-
E.
hasMedievalBuilding
Indicates that one entity possesses, contains, or includes a building dating from the medieval 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da543e74819083ebea41ca20e0e9 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:36 p.m.