Triple
T8457021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Avignon |
E199943
|
entity |
| Predicate | primaryPassengerProfile |
P63093
|
FINISHED |
| Object | leisure travellers |
—
|
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: leisure travellers | Statement: [London–Avignon, primaryPassengerProfile, leisure travellers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPassengerProfile Context triple: [London–Avignon, primaryPassengerProfile, leisure travellers]
-
A.
primaryUserType
chosen
Indicates the main or dominant category of user associated with an entity or interaction.
-
B.
primaryParticipant
Indicates that an entity plays the main or most central role in a given event, activity, or relationship.
-
C.
hasPassengerRole
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
-
D.
primaryPatientType
Indicates the main category or classification of patient that is primarily associated with or targeted by an entity, action, or service.
-
E.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe48f180c8190a71cf9d7248ade60 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.