Triple
T7625109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nantan |
E172607
|
entity |
| Predicate | hasTraditionalCulturalSites |
P78176
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nantan, hasTraditionalCulturalSites, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalCulturalSites Context triple: [Nantan, hasTraditionalCulturalSites, true]
-
A.
hasCulturalSiteType
Indicates that an entity is associated with, or classified by, a specific type or category of cultural site.
-
B.
culturalSite
Indicates that one entity is recognized or designated as a cultural site associated with or located in relation to another entity.
-
C.
isCulturalHeritageSite
Indicates that a place or structure is officially recognized and protected as having significant cultural, historical, or artistic value.
-
D.
culturalHeritageOf
Indicates that something serves as the cultural heritage belonging to, originating from, or strongly associated with a particular entity or group.
-
E.
hasUNESCOCandidateSite
Indicates that an entity possesses or includes at least one site that is a candidate for inscription on the UNESCO World Heritage List.
- F. None of above. chosen
Provenance (4 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6fe7323b0819081664662d2f26937 |
completed | March 27, 2026, 10:02 p.m. |
Created at: March 27, 2026, 3:56 p.m.