Triple
T3073743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson River National Historic Landmark District |
E64086
|
entity |
| Predicate | containsTypeOfSite |
P9088
|
FINISHED |
| Object | country estates |
—
|
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: country estates | Statement: [Hudson River National Historic Landmark District, containsTypeOfSite, country estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsTypeOfSite Context triple: [Hudson River National Historic Landmark District, containsTypeOfSite, country estates]
-
A.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
B.
coversTypeOfSite
chosen
Indicates that one entity provides coverage or applies to a particular category or type of site.
-
C.
typeOfSite
Indicates the specific category or kind of site that an entity is classified as.
-
D.
isSiteSpecific
Indicates that something is designed, intended, or valid only for a particular location, context, or site and does not generally apply elsewhere.
-
E.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14e372c81908c25c7f3e7e0c864 |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.