Triple
T24330257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheringham railway station |
E613220
|
entity |
| Predicate | hasHeritageLink |
P153856
|
FINISHED |
| Object | Poppy Line |
—
|
NE NERFINISHED |
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: Poppy Line | Statement: [Sheringham railway station, hasHeritageLink, Poppy Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageLink Context triple: [Sheringham railway station, hasHeritageLink, Poppy Line]
-
A.
hasCulturalHeritageLink
chosen
Indicates a relationship where one entity is culturally derived from, influenced by, or historically connected to another.
-
B.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
C.
hasHeritageConnectionWith
Indicates a relationship where two entities are linked through shared, inherited, or culturally transmitted heritage or ancestry.
-
D.
hasHeritageOfSite
Indicates that a site possesses or is associated with a particular heritage designation, tradition, or cultural-historical value.
-
E.
hasHeritageFeature
Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292f0539081908f2d1769ad122572 |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:55 a.m.