Triple

T24591745
Position Surface form Disambiguated ID Type / Status
Subject Singer 301 E608555 entity
Predicate designRelation P146314 FINISHED
Object mechanically related to Singer 221 Featherweight 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: mechanically related to Singer 221 Featherweight | Statement: [Singer 301, designRelation, mechanically related to Singer 221 Featherweight]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designRelation
Context triple: [Singer 301, designRelation, mechanically related to Singer 221 Featherweight]
  • A. hasDesignRelationship chosen
    Indicates that there exists a design-based relationship or association between two entities, such as one influencing, constraining, or deriving from the design of the other.
  • B. datumRelation
    Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
  • C. definesRelationshipBetween
    Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
  • D. stageRelation
    Indicates a relationship between entities based on their roles, positions, or phases within a staged process or sequence.
  • E. stepRelation
    Indicates a relationship where one entity is a step-relative of another, such as a stepparent, stepchild, or stepsibling connection.
  • 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_69e2c4cf54248190af7b0c2d9ade9830 completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a9db3a9481908c7a59281e2ca994 completed April 30, 2026, 1:01 a.m.
PD Predicate disambiguation batch_69f2a6c1f07081908edf0b521767e79b completed April 30, 2026, 12:48 a.m.
Created at: April 18, 2026, 2:30 a.m.