Triple
T9392649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Sen Yung |
E226060
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Yung |
E504165
|
NE 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: Yung | Statement: [Victor Sen Yung, familyName, Yung]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yung Context triple: [Victor Sen Yung, familyName, Yung]
-
A.
Yung
chosen
Yung is a common variant spelling of the surname and given name "Young," used in various cultures and contexts.
-
B.
Yung Gud
Yung Gud is a Swedish producer and DJ best known for his atmospheric, melancholic beats and frequent collaborations with rapper Yung Lean as part of the Sad Boys collective.
-
C.
Yung Exclusive
Yung Exclusive is a music producer best known for working on the hit track "Goosebumps."
-
D.
Yong
Yong is a variant transliteration of the Chinese surname and given name commonly romanized as Yang.
-
E.
Yong
Yong was the personal name of King Wuling of Zhao, a reformist ruler of the Warring States period in ancient China known for adopting nomadic military tactics and attire.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd510fec6481908b51c497744068c8 |
completed | April 1, 2026, 5:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d10108cd0c8190a38ee2325d3475ce |
completed | April 4, 2026, 12:16 p.m. |
Created at: March 30, 2026, 7:45 p.m.