Triple
T29312390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | country estate Horn |
E743271
|
entity |
| Predicate | hasHeritageStatusScope |
P119228
|
FINISHED |
| Object | regional 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: regional significance | Statement: [country estate Horn, hasHeritageStatusScope, regional significance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageStatusScope Context triple: [country estate Horn, hasHeritageStatusScope, regional significance]
-
A.
hasHeritageStatusContext
Indicates that an entity’s heritage status is qualified, interpreted, or contextualized by a specific situational or descriptive framework.
-
B.
hasHeritageStatusWithin
chosen
Indicates that something holds a recognized heritage designation or status within a specified area, jurisdiction, or context.
-
C.
hasHeritageCriteria
Indicates that something is associated with specific heritage criteria that define its cultural, historical, or natural significance.
-
D.
hasHeritageContext
Indicates that something is associated with, influenced by, or situated within a particular cultural, historical, or heritage-related context.
-
E.
hasHeritageServiceTo
Indicates that one entity provides heritage-related services or functions to another entity.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 28, 2026, 1:17 p.m.