Triple
T32999143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hobcaw House |
E844313
|
entity |
| Predicate | purposeOfPreservation |
P39107
|
FINISHED |
| Object | research |
—
|
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: research | Statement: [Hobcaw House, purposeOfPreservation, research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfPreservation Context triple: [Hobcaw House, purposeOfPreservation, research]
-
A.
preservationPurpose
Indicates that something exists, is created, or is maintained with the specific aim of preserving or safeguarding another entity or resource.
-
B.
reasonForPreservation
chosen
Indicates that something is being preserved or maintained for a particular reason, purpose, or justification.
-
C.
preservationUse
Indicates that something is used, designed, or intended specifically for the purpose of preserving or maintaining another entity in its existing state.
-
D.
aimsToPreserve
Indicates an intention or effort by one entity to maintain, protect, or keep another entity in its current or desired state.
-
E.
preservationCause
Indicates that one entity is the reason or factor responsible for preserving, maintaining, or keeping another entity in its existing state or condition.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:22 a.m.