Triple
T11896713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercersburg, Pennsylvania |
E283051
|
entity |
| Predicate | hasHistoricArchitectureFromCentury |
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: [Mercersburg, Pennsylvania, hasHistoricArchitectureFromCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricArchitectureFromCentury Context triple: [Mercersburg, Pennsylvania, hasHistoricArchitectureFromCentury, 18th century]
-
A.
containsBuildingFromCentury
chosen
Indicates that a location or area includes at least one building that originates from a specified century.
-
B.
constructionCentury
Indicates the century during which something was constructed or built.
-
C.
architectureHistory
Indicates a historical or developmental relationship between an entity and its architectural evolution, style, or significant architectural events over time.
-
D.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
E.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other entity.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1286808190949719f54ff49a01 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.