Triple
T106538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic General Dodge House |
E2148
|
entity |
| Predicate | preservationStatus |
P923
|
FINISHED |
| Object | preserved |
—
|
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: preserved | Statement: [Historic General Dodge House, preservationStatus, preserved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservationStatus Context triple: [Historic General Dodge House, preservationStatus, preserved]
-
A.
conservationStatus
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
-
B.
heritageStatus
chosen
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
C.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
D.
hasProtectedAreaStatus
Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
-
E.
historicalRecordStatus
Indicates the status or condition of a record within a historical or archival context (e.g., active, archived, revised, or obsolete).
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a256ec650c8190bee2067e37065527 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563d33788190999d471b486d5603 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.