Triple

T1609390
Position Surface form Disambiguated ID Type / Status
Subject Texas A&M Aggies football E34581 entity
Predicate traditionCharacteristic P30241 FINISHED
Object rich and distinctive 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: rich and distinctive | Statement: [Texas A&M Aggies football, traditionCharacteristic, rich and distinctive]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionCharacteristic
Context triple: [Texas A&M Aggies football, traditionCharacteristic, rich and distinctive]
  • A. culturalTradition
    Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
  • B. traditionAscribes
    Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
  • C. traditionSince
    Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
  • D. traditionInheritedFrom
    Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
  • E. traditionsMaintainedBy
    Indicates that certain traditions are preserved, upheld, or continued in practice by a particular entity.
  • 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_69a885fea6a481909fe83ba6441f1774 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a93fa6926081908bc78d15c0be3185 completed March 5, 2026, 8:32 a.m.
PD Predicate disambiguation batch_69a907c35f848190a2428c52e81d013e completed March 5, 2026, 4:34 a.m.
PDg Predicate description generation batch_69a93fa5aa04819084d1154ef900303f completed March 5, 2026, 8:32 a.m.
Created at: March 4, 2026, 7:28 p.m.