Triple
T34888521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal–Quebec City |
E1006216
|
entity |
| Predicate | hasTypicalPrimaryPurpose |
P125948
|
FINISHED |
| Object | business travel |
—
|
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: business travel | Statement: [Montreal–Quebec City, hasTypicalPrimaryPurpose, business travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalPrimaryPurpose Context triple: [Montreal–Quebec City, hasTypicalPrimaryPurpose, business travel]
-
A.
hasEstablishedPurpose
Indicates that an entity has a defined and recognized purpose or intended function already determined.
-
B.
hasMarketingPurpose
Indicates that something is intended or used for marketing-related purposes, such as promoting, advertising, or increasing awareness of a product, service, or brand.
-
C.
hasProtectionPurpose
Indicates that something is intended or designed to serve a protective function or goal.
-
D.
isPrimarilyUsedAs
chosen
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
E.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: May 3, 2026, 4 p.m.