Triple

T36677666
Position Surface form Disambiguated ID Type / Status
Subject Crossness Pumping Station E905585 entity
Predicate mechanicalSystem P162722 FINISHED
Object rotative beam engines 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: rotative beam engines | Statement: [Crossness Pumping Station, mechanicalSystem, rotative beam engines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mechanicalSystem
Context triple: [Crossness Pumping Station, mechanicalSystem, rotative beam engines]
  • A. mechanicalFunction
    Indicates that one entity serves as the mechanical role, operation, or function performed by another entity or system.
  • B. mechanicalDesign
    Indicates that one entity is responsible for or associated with the mechanical design or engineering configuration of another entity.
  • C. mechanicalCompatibility
    Indicates that two entities can function together properly from a mechanical standpoint, without interference, damage, or performance issues.
  • D. mechanismComponent chosen
    Indicates that one entity functions as a component or part within the structure or operation of another entity conceived as a mechanism.
  • E. mechanicalProperty
    Indicates a relationship where a mechanical characteristic (such as strength, stiffness, hardness, or elasticity) is attributed to or associated with an entity.
  • 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_69f76e7011dc819082b324f18b756a1b completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c7a3c6e08190b79f76bc3df441eb completed May 3, 2026, 10:09 p.m.
PD Predicate disambiguation batch_69f7c4796ebc819084a0dc08505e5f14 completed May 3, 2026, 9:56 p.m.
Created at: May 3, 2026, 4:12 p.m.