Triple
T32436052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai intercity coach network |
E828868
|
entity |
| Predicate | ticketLanguageSupport |
P173412
|
FINISHED |
| Object | 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: Chinese | Statement: [Shanghai intercity coach network, ticketLanguageSupport, Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketLanguageSupport Context triple: [Shanghai intercity coach network, ticketLanguageSupport, Chinese]
-
A.
eligibleLanguage
Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
-
B.
usesLanguageSupport
chosen
Indicates that one entity makes use of language-related assistance, features, or services provided by another entity.
-
C.
serviceBrandLanguage
Indicates the language or languages in which a service brand communicates or is presented.
-
D.
isSupportedByLanguage
Indicates that something (such as a feature, format, or construct) is compatible with and can be handled or recognized by a particular language.
-
E.
hasCustomerServiceLanguage
Indicates that an entity provides customer service in a specified language or set of languages.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2b48a8c8190a6ba0d2f084078cc |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:55 a.m.