Triple
T37139058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Square ensemble |
E920051
|
entity |
| Predicate | hasUNESCOSCriteria |
P1725
|
FINISHED |
| Object | (i) |
—
|
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: (i) | Statement: [Red Square ensemble, hasUNESCOSCriteria, (i)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUNESCOSCriteria Context triple: [Red Square ensemble, hasUNESCOSCriteria, (i)]
-
A.
hasUNESCOCandidateSite
Indicates that an entity possesses or includes at least one site that is a candidate for inscription on the UNESCO World Heritage List.
-
B.
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.
-
C.
isInUNESCOSiteCategory
Indicates that an entity belongs to, or is classified under, a specific UNESCO World Heritage Site category.
-
D.
hasUNESCOIdNote
Indicates that there is a note or annotation associated with an entity’s UNESCO identifier.
-
E.
unescoDesignation
Indicates that an entity has been granted a specific designation or status by UNESCO.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:15 p.m.