Triple
T19322196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas–Texas A&M baseball rivalry |
E483252
|
entity |
| Predicate | hasIntensityLevel |
P1942
|
FINISHED |
| Object | intense rivalry |
—
|
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: intense rivalry | Statement: [Texas–Texas A&M baseball rivalry, hasIntensityLevel, intense rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntensityLevel Context triple: [Texas–Texas A&M baseball rivalry, hasIntensityLevel, intense rivalry]
-
A.
isIntense
Indicates that something exhibits a high degree of strength, force, or concentration in its quality, effect, or activity.
-
B.
intensityScale
chosen
Indicates the degree or level of strength, magnitude, or severity associated with an event, property, or measurement, typically according to a defined scale.
-
C.
hasCentralIntensity
Indicates that something possesses a specific value or measure of intensity at its central point or core region.
-
D.
hasRatingLevel
Indicates that an entity is associated with a particular rating level or score category.
-
E.
hasFanIntensity
Indicates the level or strength of airflow produced by a fan in a given context.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d8948948190b76a384041333509 |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.