Triple
T27086901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United World Wrestling |
E686058
|
entity |
| Predicate | governsStyle |
P193993
|
FINISHED |
| Object | beach 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: beach wrestling | Statement: [United World Wrestling, governsStyle, beach wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsStyle Context triple: [United World Wrestling, governsStyle, beach wrestling]
-
A.
governsInStyle
Indicates that a governing entity exercises authority or leadership in a distinctive, notable, or characteristic manner.
-
B.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
-
C.
authorityStyle
Indicates the manner or approach by which authority is exercised or expressed in a relationship or context.
-
D.
governingStyleAssociatedWith
Indicates a relationship where a particular governing style, method, or approach is linked or attributed to a specific entity (such as a leader, regime, or organization).
-
E.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: April 27, 2026, 8:38 a.m.