Triple
T20315868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stagecoach Rail |
E510377
|
entity |
| Predicate | brandLifecycleEvent |
P139628
|
FINISHED |
| Object | brand retirement |
—
|
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: brand retirement | Statement: [Stagecoach Rail, brandLifecycleEvent, brand retirement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandLifecycleEvent Context triple: [Stagecoach Rail, brandLifecycleEvent, brand retirement]
-
A.
brandLifecycleContext
Indicates the stage or phase of a brand’s lifecycle that provides contextual information for interpreting related actions or relationships.
-
B.
brandLaunch
Indicates the event or action of introducing a new brand (or a major rebranding) into the market.
-
C.
brandLaunchBy
Indicates that a particular brand was introduced or brought to market by a specific agent or organization.
-
D.
brandLaunchContext
Indicates the circumstances, setting, or strategic situation in which a brand is introduced or launched.
-
E.
brandLaunchPurpose
Indicates the strategic goal or primary intent behind launching a particular brand.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67787af188190bc32a3049c9c5b39 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:19 a.m.