Triple
T27051160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunqu |
E684775
|
entity |
| Predicate | inscribedAsUNESCOYear |
P152553
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Kunqu, inscribedAsUNESCOYear, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscribedAsUNESCOYear Context triple: [Kunqu, inscribedAsUNESCOYear, 2001]
-
A.
inscribedOnUNESCOListInYear
Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
-
B.
yearOfUNESCORecognition
chosen
Indicates the specific year in which something was officially recognized or inscribed by UNESCO.
-
C.
UNESCOInscribedBy
Indicates that a site, object, or element has been formally inscribed or designated by UNESCO, typically on one of its official heritage or recognition lists.
-
D.
UNESCOTransferYear
Indicates the year in which responsibility, ownership, or designation of something was formally transferred under the authority or framework of UNESCO.
-
E.
recognizedAsFirstUNESCOSiteIn
Indicates that an entity is acknowledged as the first UNESCO World Heritage Site within a specified place or jurisdiction.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 8:14 a.m.