Triple
T38188646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto–Ottawa |
E1005389
|
entity |
| Predicate | supportsTravelPurpose |
P102055
|
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: [Toronto–Ottawa, supportsTravelPurpose, business travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTravelPurpose Context triple: [Toronto–Ottawa, supportsTravelPurpose, business travel]
-
A.
appliesToTravelType
Indicates that something is relevant or restricted to a specific type or category of travel.
-
B.
validForTravelTo
Indicates that something (such as a document, item, or condition) is acceptable or authorized for use when traveling to a specified destination.
-
C.
journeyPurpose
chosen
Indicates the reason or intended goal motivating an entity’s journey or trip.
-
D.
travelsFor
Indicates that one entity moves from place to place on behalf of, or for the benefit or purpose of, another entity or objective.
-
E.
allowsTravelAcross
Indicates that one entity enables or permits movement or passage from one side or location to another across a separating space or boundary.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:29 p.m.