Triple
T1049463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Euston – Manchester |
E22660
|
entity |
| Predicate | typicalJourneyPurpose |
P24037
|
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: [London Euston – Manchester, typicalJourneyPurpose, business travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalJourneyPurpose Context triple: [London Euston – Manchester, typicalJourneyPurpose, business travel]
-
A.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
B.
coTraveler
Indicates that two or more entities are traveling together along (part of) the same journey or route.
-
C.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
D.
travelPreference
Indicates a person's favored way or style of traveling, such as preferred modes, conditions, or arrangements for trips.
-
E.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
- F. None of above. chosen
Provenance (4 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8f1097881908932d7eea4331917 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:42 p.m.