Triple
T16253776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perfect World |
E394577
|
entity |
| Predicate | onlineServiceStatus |
P5871
|
FINISHED |
| Object | operational in some regions |
—
|
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: operational in some regions | Statement: [Perfect World, onlineServiceStatus, operational in some regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onlineServiceStatus Context triple: [Perfect World, onlineServiceStatus, operational in some regions]
-
A.
serviceAvailability
chosen
Indicates whether a particular service is accessible and operational for use during a given time or under specified conditions.
-
B.
typicalServiceStatus
Indicates the usual or standard operational state or condition that a service is expected to be in under normal circumstances.
-
C.
serviceNumberStatus
Indicates the current operational or availability state associated with a specific service number.
-
D.
operatesOnlineService
Indicates that an entity runs or manages an online service or platform for others to use.
-
E.
platformStatus
Indicates the current operational or availability state of a platform within a system or service context.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24598c9488190a92df7d8b1824724 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.