Triple
T19529361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dangun myth |
E488617
|
entity |
| Predicate | linkedEthnicSymbol |
P53164
|
FINISHED |
| Object | bear totem |
—
|
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: bear totem | Statement: [Dangun myth, linkedEthnicSymbol, bear totem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedEthnicSymbol Context triple: [Dangun myth, linkedEthnicSymbol, bear totem]
-
A.
linkedToEthnicIdentity
Indicates a relationship where something is associated or connected with a particular ethnic identity.
-
B.
equivalentEthnonym
Indicates that two different ethnonyms refer to the same ethnic group or people.
-
C.
associatedEthnicityOfBearer
Indicates the ethnic group or ethnicity with which the bearer of something (such as a name, title, or item) is associated.
-
D.
symbolLinked
chosen
Indicates a relationship where one symbol is connected or associated with another symbol, typically to show reference, correspondence, or linkage between them.
-
E.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363dfd6c8190aaa0b374184965bb |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.