Triple
T748491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division II Wrestling |
E15394
|
entity |
| Predicate | wrestlingStyle |
P3775
|
FINISHED |
| Object | folkstyle wrestling |
—
|
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: folkstyle wrestling | Statement: [NCAA Division II Wrestling, wrestlingStyle, folkstyle wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrestlingStyle Context triple: [NCAA Division II Wrestling, wrestlingStyle, folkstyle wrestling]
-
A.
wrestledWith
Indicates that one entity engaged in a physical wrestling contest or struggle with another entity.
-
B.
boxingStance
Indicates the specific posture or positioning a boxer adopts while preparing to fight or engage in boxing actions.
-
C.
styleOfPlay
chosen
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
D.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
E.
weightClass
Indicates the categorical grouping of an entity based on its weight range or mass classification.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a62f31888190b80cb0a7220f8d80 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.