Triple
T29172488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OC Bus |
E739507
|
entity |
| Predicate | languageOfCustomerInformation |
P112988
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [OC Bus, languageOfCustomerInformation, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCustomerInformation Context triple: [OC Bus, languageOfCustomerInformation, English]
-
A.
languageOfCustom
Indicates that a particular language is used to express, perform, or transmit a given custom or cultural practice.
-
B.
hasCustomerServiceLanguage
chosen
Indicates that an entity provides customer service in a specified language or set of languages.
-
C.
primaryLanguageOnCard
Indicates that a specified language is the main or dominant language used on a given card.
-
D.
languageOfProduct
Indicates the language in which a product is written, labeled, presented, or otherwise 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 28, 2026, 11:53 a.m.