Triple
T2310142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Lancashire Railway |
E51934
|
entity |
| Predicate | operatesEvent |
P24921
|
FINISHED |
| Object | steam gala events |
—
|
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: steam gala events | Statement: [East Lancashire Railway, operatesEvent, steam gala events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesEvent Context triple: [East Lancashire Railway, operatesEvent, steam gala events]
-
A.
operatesFestival
chosen
Indicates that one entity manages and runs the organization or execution of a festival for another entity or in a particular context.
-
B.
operatesVenue
Indicates that one entity manages and runs the day-to-day operations of a particular venue.
-
C.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
D.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
E.
operatesService
Indicates that an agent runs, manages, or provides a particular service.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.