Triple
T130254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sever Hall |
E2638
|
entity |
| Predicate | heritageCriteria |
P1725
|
FINISHED |
| Object | architectural 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: architectural significance | Statement: [Sever Hall, heritageCriteria, architectural significance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageCriteria Context triple: [Sever Hall, heritageCriteria, architectural significance]
-
A.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
B.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
C.
heritageManagement
Indicates the management, preservation, and regulation of cultural or natural heritage resources by responsible entities.
-
D.
UNESCOWorldHeritageCriteria
chosen
Indicates that a site meets one or more of the official UNESCO World Heritage criteria used to justify its inscription on the World Heritage List.
-
E.
heritageDesignation
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564da96c8190aa8204de25229c15 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.