Triple

T21506964
Position Surface form Disambiguated ID Type / Status
Subject Reports on the effect of railroad rebates on competition E530619 entity
Predicate conclusionTopic P61768 FINISHED
Object distortion of competitive conditions by rebates 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: distortion of competitive conditions by rebates | Statement: [Reports on the effect of railroad rebates on competition, conclusionTopic, distortion of competitive conditions by rebates]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conclusionTopic
Context triple: [Reports on the effect of railroad rebates on competition, conclusionTopic, distortion of competitive conditions by rebates]
  • A. concludesAbout chosen
    Indicates that one entity forms or states a conclusion regarding another entity or its properties.
  • B. conclusionType
    Indicates the specific kind or category of conclusion associated with an argument, inference, or reasoning process.
  • C. typicalConclusion
    Indicates that one entity is the usual or expected outcome, result, or ending that follows from another entity or situation.
  • D. concludingIssue
    Indicates that an issue represents the final or closing installment in a sequence, series, or publication run.
  • E. closingTopic
    Indicates that one entity brings a discussion, issue, or conversational thread to an end or final resolution.
  • 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_69e0c45c81f08190a6b8bbb70a45aae7 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9ea7d8be881908ff8a58b8a6eff40 completed April 23, 2026, 9:46 a.m.
PD Predicate disambiguation batch_69e631f6e68081908f5ee4ce7413803e completed April 20, 2026, 2:02 p.m.
Created at: April 16, 2026, 6:24 p.m.