Triple
T20791061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 NCAA women’s gymnastics championship |
E511776
|
entity |
| Predicate | apparatusContested |
P141553
|
FINISHED |
| Object | vault |
—
|
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: vault | Statement: [2022 NCAA women’s gymnastics championship, apparatusContested, vault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apparatusContested Context triple: [2022 NCAA women’s gymnastics championship, apparatusContested, vault]
-
A.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
B.
controlContested
Indicates that authority or dominance over something is disputed or challenged between two or more parties.
-
C.
frequentlyContestedBy
Indicates that something is often the subject of disputes, challenges, or opposition initiated by another party.
-
D.
wasContestedIn
Indicates that an event, position, or decision was the subject of competition, dispute, or challenge within a particular context or proceeding.
-
E.
alsoContestedIn
Indicates that the same issue, claim, or matter is being disputed or challenged in another context, case, or proceeding as well.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c29010508190bf2cf577d7f64754 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:38 p.m.