Triple
T34800581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prevost Car |
E1003207
|
entity |
| Predicate | typicalUseOfProducts |
P131315
|
FINISHED |
| Object | intercity coach service |
—
|
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: intercity coach service | Statement: [Prevost Car, typicalUseOfProducts, intercity coach service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUseOfProducts Context triple: [Prevost Car, typicalUseOfProducts, intercity coach service]
-
A.
productsUsedIn
Indicates that certain products are utilized or applied within a particular process, context, or entity.
-
B.
endUseOfProducts
Indicates the point at which the use or consumption of products is completed or discontinued.
-
C.
primaryUseOf
chosen
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
D.
usedForProduct
Indicates that one entity serves as a tool, component, or means specifically employed in the creation, operation, or delivery of another entity considered as a product.
-
E.
usesProduct
Indicates that one entity makes use of, applies, or employs a particular product.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.