Triple
T6493934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona Wildcats gymnastics program |
E148107
|
entity |
| Predicate | primaryCompetitionFormat |
P2673
|
FINISHED |
| Object | team and individual events |
—
|
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: team and individual events | Statement: [Arizona Wildcats gymnastics program, primaryCompetitionFormat, team and individual events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCompetitionFormat Context triple: [Arizona Wildcats gymnastics program, primaryCompetitionFormat, team and individual events]
-
A.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
primaryCompetition
Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
-
C.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
D.
primaryCompetitionLevel
Indicates the main or highest level of competition at which an entity primarily competes or operates.
-
E.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an entity.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06ab7c0b8819091437a293b40dfd2 |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:53 p.m.