Triple

T1049644
Position Surface form Disambiguated ID Type / Status
Subject Virgin CrossCountry E22664 entity
Predicate franchiseEndReason P17425 FINISHED
Object franchise re-letting 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: franchise re-letting | Statement: [Virgin CrossCountry, franchiseEndReason, franchise re-letting]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: franchiseEndReason
Context triple: [Virgin CrossCountry, franchiseEndReason, franchise re-letting]
  • A. losingFranchise
    Indicates that one entity ceases to hold or control a franchise previously granted to it by another entity.
  • B. franchiseStatus chosen
    Indicates the current standing or condition of a franchise relationship between parties, such as whether it is active, inactive, pending, or terminated.
  • C. reasonForDisbandment
    Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
  • D. redeemabilityEndedReason
    Indicates the reason why the ability to redeem something (e.g., a product, offer, or asset) has ended.
  • E. reasonForDiscontinuation
    Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
  • 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_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.
Created at: March 1, 2026, 7:42 p.m.