Triple
T24281109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Treasure of South Korea |
E605541
|
entity |
| Predicate | firstDesignations |
P105492
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [National Treasure of South Korea, firstDesignations, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDesignations Context triple: [National Treasure of South Korea, firstDesignations, 1960s]
-
A.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
B.
previousDesignationIncludes
Indicates that an entity’s earlier or former official name, title, or designation contained the specified value.
-
C.
initiallyDesignated
chosen
Indicates that an entity was assigned or specified in a particular role, state, or configuration at the beginning of a process or time period.
-
D.
previousDesignationEstablished
Indicates that an earlier official designation or title for an entity was formally created or put into effect.
-
E.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5227888190b1713af150fa30a1 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.