Triple
T11453776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blawenburg Historic District |
E271469
|
entity |
| Predicate | isPreservedFor |
P90372
|
FINISHED |
| Object | historic significance |
—
|
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: historic significance | Statement: [Blawenburg Historic District, isPreservedFor, historic significance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPreservedFor Context triple: [Blawenburg Historic District, isPreservedFor, historic significance]
-
A.
somePreservedAs
Indicates that at least one part or instance of an entity is kept or maintained in a particular state, form, or condition.
-
B.
isKeptFor
chosen
Indicates that one entity is retained or preserved for the benefit, use, or purpose of another entity.
-
C.
isKeptAs
Indicates that one entity is maintained, preserved, or retained by another entity, often implying possession, storage, or ongoing custody.
-
D.
isKeptBy
Indicates that something is maintained, possessed, or held in the care or custody of a particular entity.
-
E.
partlyPreservedAs
Indicates that an entity is only partially preserved or remains in incomplete form within another entity or context.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.