Triple
T37749630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonic limited express |
E940943
|
entity |
| Predicate | languageOfServiceAnnouncements |
P6898
|
FINISHED |
| Object | Japanese |
—
|
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: Japanese | Statement: [Sonic limited express, languageOfServiceAnnouncements, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfServiceAnnouncements Context triple: [Sonic limited express, languageOfServiceAnnouncements, Japanese]
-
A.
languageOfOfficialAnnouncements
chosen
Indicates the language used for formal or official public announcements issued by an authority.
-
B.
serviceBrandLanguage
Indicates the language or languages in which a service brand communicates or is presented.
-
C.
laterLanguageOfServices
Indicates that one language is used for services at a later time or stage than another language.
-
D.
languageOfSupportMaterials
Indicates the language in which support or help materials are provided or made available.
-
E.
languageOfProvision
Indicates the language in which a provision, such as a legal or contractual clause, is written or officially expressed.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01ade363088190b3a3e3dedabd1aa2 |
completed | May 11, 2026, 10:22 a.m. |
| PD | Predicate disambiguation | batch_6a01acf3c5788190932bd8fcf27c123d |
completed | May 11, 2026, 10:18 a.m. |
Created at: May 3, 2026, 4:19 p.m.