Triple

T24237313
Position Surface form Disambiguated ID Type / Status
Subject Houston Texans Ring of Honor E603118 entity
Predicate hasInductionLimit P116659 FINISHED
Object no fixed number of inductees per year 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: no fixed number of inductees per year | Statement: [Houston Texans Ring of Honor, hasInductionLimit, no fixed number of inductees per year]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInductionLimit
Context triple: [Houston Texans Ring of Honor, hasInductionLimit, no fixed number of inductees per year]
  • A. hasInducteeLimit chosen
    Indicates that there is a maximum number of inductees allowed for a given context or event.
  • B. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • C. hasLimitation
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • D. hasInductionSchedule
    Indicates that an entity is associated with a defined plan or timetable for its induction or onboarding process.
  • E. hasLimitSet
    Indicates that there is a defined boundary, range, or constraint applied to something.
  • 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_69e2953f631c819097cbb421046bd417 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f28a9c5c3081909cfddc8d29121817 completed April 29, 2026, 10:47 p.m.
PD Predicate disambiguation batch_69f1c448abec8190b87cbf9ed419a309 completed April 29, 2026, 8:41 a.m.
Created at: April 18, 2026, 12:03 a.m.