Triple
T31057667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Shrine |
E791438
|
entity |
| Predicate | typeOfHeritageSite |
P5929
|
FINISHED |
| Object | religious heritage site |
—
|
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: religious heritage site | Statement: [National Shrine, typeOfHeritageSite, religious heritage site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfHeritageSite Context triple: [National Shrine, typeOfHeritageSite, religious heritage site]
-
A.
heritageType
chosen
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
-
B.
heritageSiteTypeNearby
Indicates that a particular type of heritage site is located in close proximity to the referenced entity.
-
C.
UNESCOSiteType
Indicates the classification of a UNESCO World Heritage Site according to its type (e.g., cultural, natural, or mixed).
-
D.
hasCulturalSiteType
Indicates that an entity is associated with, or classified by, a specific type or category of cultural site.
-
E.
typeOfLandmark
Indicates the specific category or kind of landmark that an entity belongs to (e.g., monument, natural feature, building).
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: April 29, 2026, 9 p.m.