Triple
T19225414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas–Texas A&M football rivalry |
E480725
|
entity |
| Predicate | annualFrequency |
P20895
|
FINISHED |
| Object | typically played once per season |
—
|
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: typically played once per season | Statement: [Texas–Texas A&M football rivalry, annualFrequency, typically played once per season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualFrequency Context triple: [Texas–Texas A&M football rivalry, annualFrequency, typically played once per season]
-
A.
isAnnual
chosen
Indicates that something occurs, is scheduled, or is valid once every year.
-
B.
annualFrom
Indicates that something recurs or is calculated on a yearly basis starting from a specified point in time.
-
C.
annualPractice
Indicates that an action, event, or behavior occurs as a recurring practice on a yearly basis.
-
D.
annualVisitation
Indicates a recurring visit or attendance that takes place once every year between the related entities.
-
E.
hasSeasonFrequency
Indicates how often something occurs or is scheduled within a specific season.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa97287c8190b85184a512a9c960 |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:24 p.m.