Triple
T6124672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 애국가 |
E136565
|
entity |
| Predicate | 조성 |
P21731
|
FINISHED |
| Object | A♭장조(통상 편곡 기준) |
—
|
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: A♭장조(통상 편곡 기준) | Statement: [애국가, 조성, A♭장조(통상 편곡 기준)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 조성 Context triple: [애국가, 조성, A♭장조(통상 편곡 기준)]
-
A.
Xiaoerjing
Indicates a relationship where something is written, represented, or transcribed using the Xiaoerjing (Arabic-based) script for Sinitic languages.
-
B.
ChineseLeader
Indicates that the subject is a person who holds or has held a top political leadership position in China.
-
C.
sungAs
chosen
Indicates that something is performed or vocalized in the manner, role, or identity specified by another entity (e.g., a song or part being sung as a particular character, style, or version).
-
D.
SakaeIs
Indicates that one entity is identified as or classified as "Sakae" in relation to another entity or context.
-
E.
coPrince
Indicates a relationship in which two or more individuals simultaneously share and exercise the rank and authority of prince over the same domain or polity.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05c2791948190ba33458edfd1ebe8 |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.