Triple
T32476263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revaty limited express |
E829983
|
entity |
| Predicate | serviceNameLanguage |
P56949
|
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: [Revaty limited express, serviceNameLanguage, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceNameLanguage Context triple: [Revaty limited express, serviceNameLanguage, Japanese]
-
A.
serviceBranchLanguage
Indicates the language or languages used or officially recognized by a particular branch of a service (such as a military or organizational branch).
-
B.
serviceBrandLanguage
chosen
Indicates the language or languages in which a service brand communicates or is presented.
-
C.
languageOfWorkRecognized
Indicates that a work is officially recognized as being created or expressed in a particular language.
-
D.
currentLanguageOfServices
Indicates that a specified language is the one presently used to provide or deliver certain services.
-
E.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 12:58 a.m.