Triple
T31717851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mo Yan |
E809494
|
entity |
| Predicate | hasPenNameMeaning |
P193199
|
FINISHED |
| Object | "don’t speak" in Chinese |
—
|
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: "don’t speak" in Chinese | Statement: [Mo Yan, hasPenNameMeaning, "don’t speak" in Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPenNameMeaning Context triple: [Mo Yan, hasPenNameMeaning, "don’t speak" in Chinese]
-
A.
hasGivenNameMeaning
Indicates that a given name carries a particular meaning or semantic interpretation.
-
B.
hasPenNameSubject
Indicates that the subject entity uses or is known by a particular pen name or pseudonym.
-
C.
isMeaningOfName
Indicates that one entity expresses or defines the meaning or interpretation of a given name.
-
D.
nickNameMeaning
Indicates that a nickname is associated with a particular meaning, interpretation, or significance.
-
E.
pseudonymPurpose
Indicates that a pseudonym is used for a specific purpose, function, or intended use in a given context.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
| PDg | Predicate description generation | batch_69fd3a6905b88190ae12b43576f4cc63 |
completed | May 8, 2026, 1:20 a.m. |
Created at: April 30, 2026, 11:17 p.m.