Triple
T26730642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluebell Railway |
E673961
|
entity |
| Predicate | hasHeritageEraRepresentation |
P36399
|
FINISHED |
| Object | pre-grouping era |
—
|
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: pre-grouping era | Statement: [Bluebell Railway, hasHeritageEraRepresentation, pre-grouping era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageEraRepresentation Context triple: [Bluebell Railway, hasHeritageEraRepresentation, pre-grouping era]
-
A.
hasEraInfluence
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
-
B.
representsEra
chosen
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
-
C.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time period.
-
D.
hasEraTheme
Indicates that something is associated with, characterized by, or themed around a particular historical or cultural era.
-
E.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 3:44 a.m.