Triple
T25895754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tongdosa |
E652464
|
entity |
| Predicate | heritageStatusNumber |
P1487
|
FINISHED |
| Object | 52 |
—
|
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: 52 | Statement: [Tongdosa, heritageStatusNumber, 52]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageStatusNumber Context triple: [Tongdosa, heritageStatusNumber, 52]
-
A.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
B.
heritageStatusOfCountry
Indicates the official heritage designation or status assigned to a country, typically reflecting its cultural, historical, or natural significance.
-
C.
heritageId
Indicates that one entity serves as the heritage identifier or heritage reference code associated with another entity.
-
D.
heritageState
Indicates that an entity is recognized or designated as being in a particular heritage-related condition or status (e.g., protected, endangered, or preserved).
-
E.
heritageDesignationNumber
chosen
Indicates the specific official identification number assigned to an entity as part of its heritage or cultural protection designation.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 22, 2026, 8:23 a.m.