Triple
T14321760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenwood Historic District |
E355105
|
entity |
| Predicate | isPreservationPriority |
P113975
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Greenwood Historic District, isPreservationPriority, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPreservationPriority Context triple: [Greenwood Historic District, isPreservationPriority, true]
-
A.
hasPreservationType
Indicates the specific method or category of preservation applied to an entity (e.g., how it is stored, conserved, or kept intact).
-
B.
betterPreservedThan
Indicates that one entity is in a superior state of preservation or condition compared to another entity.
-
C.
preservationFactor
Indicates the degree to which something is protected, maintained, or kept intact over time, often moderating how much change, loss, or degradation occurs.
-
D.
hasSubjectOfPreservation
Indicates that something is the specific focus or object being preserved or conserved within a preservation relationship.
-
E.
preservationType
Indicates the method or process by which something is preserved or kept from deterioration.
- F. None of above. chosen
Provenance (4 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883bf71c8190a9a092a025cf98f0 |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e9ded24819099200349cf80e068 |
completed | April 14, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:13 a.m.