Triple
T37874193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NetEase |
E944676
|
entity |
| Predicate | publishedInChina |
P180857
|
FINISHED |
| Object | World of Warcraft |
—
|
NE NERFINISHED |
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: World of Warcraft | Statement: [NetEase, publishedInChina, World of Warcraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishedInChina Context triple: [NetEase, publishedInChina, World of Warcraft]
-
A.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
B.
releaseDateChina
Indicates the date on which something (such as a product, work, or media) is officially released or made available in China.
-
C.
publishedTo
Indicates that something has been made publicly available or distributed to an audience, platform, or destination.
-
D.
returnedToChina
Indicates that an entity went back to China after having been away.
-
E.
introducedToChina
chosen
Indicates that an entity was brought or presented to China for the first time or for initial adoption or exposure.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
Created at: May 3, 2026, 4:19 p.m.