Triple
T32586447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Prince of Korea |
E832934
|
entity |
| Predicate | CrownPrincessKoreanName |
P174627
|
FINISHED |
| Object | 왕세자빈 |
—
|
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: 왕세자빈 | Statement: [Crown Prince of Korea, CrownPrincessKoreanName, 왕세자빈]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CrownPrincessKoreanName Context triple: [Crown Prince of Korea, CrownPrincessKoreanName, 왕세자빈]
-
A.
crownPrinceFrom
Indicates that one entity is the crown prince originating from, or holding that title in relation to, another entity (typically a country, state, or royal house).
-
B.
notableCrownPrincess
Indicates that the person holds or held the title of crown princess and is distinguished or noteworthy in that role.
-
C.
hasCrownName
Indicates that an entity possesses or is identified by a specific crown name, typically used as an official or regal title.
-
D.
princessOf
Indicates that one entity holds the royal title or role of princess in relation to another entity, typically a realm, family, or sovereign.
-
E.
crownCoRuler
Indicates a relationship where two or more individuals are jointly crowned and officially recognized as co-rulers of the same realm or title.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c66df4f48190b118f51553cd8437 |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c2df27ec8190912ec8eb488836d0 |
completed | May 3, 2026, 3:37 a.m. |
Created at: May 1, 2026, 1:04 a.m.