Triple
T19225505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lone Star rivalry |
E480727
|
entity |
| Predicate | conferenceChangeImpact |
P39609
|
FINISHED |
| Object | Texas A&M move to SEC in 2012 |
—
|
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: Texas A&M move to SEC in 2012 | Statement: [Lone Star rivalry, conferenceChangeImpact, Texas A&M move to SEC in 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceChangeImpact Context triple: [Lone Star rivalry, conferenceChangeImpact, Texas A&M move to SEC in 2012]
-
A.
conferenceChange
Indicates a change in some aspect of a conference, such as its schedule, location, participants, or configuration.
-
B.
conferenceChangeContext
Indicates a change in the state, scope, or parameters of a conference-related interaction or session.
-
C.
conferenceRealignmentEffect
chosen
Indicates the impact that a change in conference membership or structure has on the entities involved.
-
D.
conference2
Indicates that one entity is a conference or event that is associated with, hosted by, or otherwise related to another entity.
-
E.
conferenceServed
Indicates that a particular conference provided services, resources, or support to a specified entity (such as attendees, organizations, or events).
- 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.