Triple

T33648093
Position Surface form Disambiguated ID Type / Status
Subject Corris Railway E862015 entity
Predicate hasPrimaryMaterialCarriedHistorically P203623 FINISHED
Object slate — 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: slate | Statement: [Corris Railway, hasPrimaryMaterialCarriedHistorically, slate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPrimaryMaterialCarriedHistorically
Context triple: [Corris Railway, hasPrimaryMaterialCarriedHistorically, slate]
  • A. hasHistoricalOccupationMaterial
    Indicates that something is composed of or contains material evidence related to past occupations or uses by people.
  • B. historicallyMadeOf
    Indicates that something was typically or traditionally constructed from a particular material in the past, even if that may no longer be the case.
  • C. hasArchaeologicalMaterial
    Indicates that an entity possesses, contains, or is associated with specific archaeological materials or artifacts.
  • D. containsMaterialFromPeriod
    Indicates that something includes material originating from or associated with a specified historical or temporal period.
  • E. hasPrimaryUseHistoric
    Indicates that something is primarily used for historic or heritage-related purposes.
  • 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_69f349840ba881908e3bfce536aeb92b completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_6a01b50490e481908eb1d675561fdde2 completed May 11, 2026, 10:52 a.m.
PD Predicate disambiguation batch_6a01b44b106481908aa98a3f1eb2c119 completed May 11, 2026, 10:49 a.m.
PDg Predicate description generation batch_6a01b503aafc81908c9e38c2f3b68016 completed May 11, 2026, 10:52 a.m.
Created at: May 1, 2026, 1:42 a.m.