Triple

T18216456
Position Surface form Disambiguated ID Type / Status
Subject Monon Bell Classic E436171 entity
Predicate hasSeriesRecord P130286 FINISHED
Object long‑running series between DePauw and Wabash 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: long‑running series between DePauw and Wabash | Statement: [Monon Bell Classic, hasSeriesRecord, long‑running series between DePauw and Wabash]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSeriesRecord
Context triple: [Monon Bell Classic, hasSeriesRecord, long‑running series between DePauw and Wabash]
  • A. hasSeriesStructure
    Indicates that one entity is organized as a sequence or series of related components or parts.
  • B. hasSeriesDefinition
    Indicates that something is associated with a specific series-level definition that characterizes or constrains it.
  • C. hasSeriesNumber
    Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
  • D. hasMainSeriesEntry
    Indicates that an entity is a primary or canonical installment within a larger series or sequence of related works.
  • E. hasStandardSeries
    Indicates that an entity is associated with, or belongs to, a designated standard series or standardized sequence.
  • 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_69d8b9103a8081908bbb0836fef10efd completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e47765a081908d0bbca1245f89ba completed April 19, 2026, 2:19 p.m.
PD Predicate disambiguation batch_69e4332155d88190b106d0dceb4554af completed April 19, 2026, 1:42 a.m.
PDg Predicate description generation batch_69e438f684e48190b38c64b58c518b6a completed April 19, 2026, 2:07 a.m.
Created at: April 10, 2026, 10:32 a.m.