Triple
T11537224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kościuszko Mound in Kraków |
E273580
|
entity |
| Predicate | heritageStatusGrantedInYear |
P13050
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Kościuszko Mound in Kraków, heritageStatusGrantedInYear, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageStatusGrantedInYear Context triple: [Kościuszko Mound in Kraków, heritageStatusGrantedInYear, 2002]
-
A.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
B.
heritageDesignationStartTime
Indicates the point in time when an entity was officially granted a particular heritage designation.
-
C.
heritageRevelationYear
Indicates the year in which a particular heritage status, designation, or significance was formally revealed, recognized, or made public.
-
D.
heritageDesignationGrantedBy
Indicates that an entity’s heritage designation or protected status has been formally conferred by a specific authority or organization.
-
E.
heritageDesignationYear
chosen
Indicates the year in which something was formally granted a particular heritage designation or status.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8839cdf688190ae75c0e6fece8e33 |
completed | April 10, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.