Triple
T13602338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Funnel |
E324973
|
entity |
| Predicate | serviceContinuity |
P14583
|
FINISHED |
| Object | year-round operation |
—
|
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: year-round operation | Statement: [Red Funnel, serviceContinuity, year-round operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceContinuity Context triple: [Red Funnel, serviceContinuity, year-round operation]
-
A.
primaryContinuityOf
Indicates that one entity serves as the main or principal continuation or extension of another entity in a sequence or process.
-
B.
continuityStatus
chosen
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
-
C.
serviceContinuationEra
Indicates the historical or temporal period during which a service continues to operate or remain in effect.
-
D.
continuedInServiceOn
Indicates that an entity remained active, operational, or in use beyond a specified point in time or event.
-
E.
serviceDuring
Indicates that one entity performs or provides a service for another entity during a specified time period or event.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb07ad3f48190a2173e42c5cfedb1 |
completed | April 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.