Triple
T15327957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division II women's gymnastics |
E366460
|
entity |
| Predicate | apparatus |
P101141
|
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: [NCAA Division II women's gymnastics, apparatus, vault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apparatus Context triple: [NCAA Division II women's gymnastics, apparatus, vault]
-
A.
describesApparatus
Indicates that one entity provides a description or specification of an apparatus used by another entity or within a particular context.
-
B.
notableGroundEquipment
Indicates that there is ground-based equipment at or associated with an entity that is considered significant or noteworthy in some context.
-
C.
typeOfEquipmentUsed
chosen
Indicates that a particular piece or category of equipment is utilized in performing a specific action, process, or activity.
-
D.
equipmentIncludes
Indicates that one entity contains, comprises, or has as part of its set of items a specified piece or set of equipment.
-
E.
missionEquipment
Indicates that certain equipment is assigned to, used for, or associated with carrying out a specific mission.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dffd6f88190a0f031ee90c6a7d2 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.